Question

Your team publishes an internal npm library to GitHub Packages. Consuming teams should only receive automatic updates for backward-compatible bug fixes when they use a caret (^) version range, but they must explicitly opt in to test unstable builds produced from feature branches. Which versioning approach should you configure in the publish pipeline?

Accepted Answer

Publish stable releases with SemVer patch increments (e.g., 2.4.1) and publish feature-branch builds as pre-release versions with a suffix (e.g., 2.5.0-beta.3)

Answer

Publish every build using CalVer (e.g., 2024.06.14) so consumers always get the latest dated package via the caret range

Answer

Publish stable and feature-branch builds with incrementing major versions (e.g., 3.0.0, 4.0.0) so caret ranges pick up all changes automatically

Answer

Publish all builds as the same version and overwrite the package each time, relying on the feed to serve the newest upload