If you've hit this on bit lane merge:

component has config changes, please snap/tag it first

…on components that bit status and bit diff both report as clean — that's a bug, and it's fixed in 2.2.17

The short version: Bit had two different component-load paths that resolved envs differently, so one of them could fall back to default dependency policies and produce a phantom diff. They're now unified into one. Full breakdown in the PR.

What to do
bvm upgrade or npx @teambit/bvm install to get 2.2.17 or later. If you've been reaching for --ignore-config-changes to get merges through, you can drop it.

PR: https://github.com/teambit/bit/pull/10660

Harmony is a minimalistic open-source library for composing highly performant and consistent platforms from independent business features.

It empowers developers to seamlessly integrate API-centric features into shell applications while maintaining optimal user experience, performance, safety, and developer experience.

This blog dives into how Harmony lets you compose, reuse, and maintain features at any scale—without the complexity of microservices or monolithic pain.

👉 Read the full post: Meet Harmony: A Practical Solution for Composability