In semantic versioning, what does a MINOR version bump typically indicate?

• A. Backwards-incompatible changes.
• B. Backwards-compatible feature additions.
• C. Security hotfix.
• D. Documentation update.

Answer: (B)

In semantic versioning, the minor version bump signals the addition of new features in a way that remains backwards compatible with existing code. That means you can upgrade to a new minor version without breaking existing applications or APIs; developers can start using the new features if they want, while existing functionality continues to work as before. An example would be adding a new API endpoint or a new configuration option that doesn’t alter or remove what was already available.

By contrast, a major version bump would indicate backwards-incompatible changes, a patch version bump covers backwards-compatible bug fixes, and documentation updates typically don’t justify a minor version bump on their own.