Use commit and version labels that communicate feature, fix, and breaking-change intent.
SemVer MAP What do Major, Minor, and Patch communicate? Compatibility, not effort. Commit title Which commit title carries useful release intent? Use type and scope to reduce release archaeology. Breaking change Only one internal app uses this response field, so it is not really breaking. A consumer depends on the field even if the consumer is internal. Your line If a consumer must change code, mark it as breaking and include the migration path. Internal dependencies are still dependencies. Compatibility signals protect downstream teams from surprise work. Scope What should a commit scope name? Think affected area. The package, feature,…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in