1 / 5
Under semantic versioning, a backwards-incompatible change requires bumping the ___ version.
-
-
-
-
SemVer increments the major number (e.g. 2.x to 3.0) for breaking changes, signalling users must review before upgrading.
2 / 5
A changelog section that warns users an API was removed should be labelled ___.
-
-
-
-
A clearly marked Breaking Changes section helps users spot what could break their integration at a glance.
3 / 5
Telling users exactly how to update their code for a breaking change is a ___ guide.
-
-
-
-
Migration notes (before/after snippets, renamed options) reduce upgrade friction and support requests.
4 / 5
Listing contributors' names in the release notes is a way to ___ them.
-
-
-
-
Crediting contributors recognises their work publicly and motivates ongoing community participation.
5 / 5
A bug fix with no API change should normally be a ___ release.
-
-
-
-
SemVer uses the patch number (e.g. 1.4.2 to 1.4.3) for backwards-compatible bug fixes, so users can upgrade safely.