chore: bump version to 1.4.0 - #397
Open
sarve-shreyas wants to merge 1 commit into
Open
Conversation
…server.json 1.3.2 -> 1.4.0. A minor bump because the release it unblocks adds a new tool (askBrowserStackAI) and declared preconditions across 22 existing ones; 1.3.x has been carrying patches. Separate from the feature PR on review feedback (#379 finding 7): a bump does not belong in a feature diff, and repo convention is its own PR. #379 is back on 1.3.2 and stays there. server.json's top-level `version` is deliberately untouched at 1.0.0 — that is the server-entry schema version. The package version lives in `packages[].version`, which is what #396 moved, and what moves here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
1.3.2 → 1.4.0, in the three files that move in lockstep percommit-conventions.md:package.jsonversionpackage-lock.jsonversionandpackages[""].versionserver.jsonpackages[].versionNote
server.json's top-levelversionstays1.0.0— that's the server-entry schema version, not the package version. Only the entry insidepackagestracks releases, which is how #396 did it.Why minor, not patch
The release this unblocks adds a new tool (
askBrowserStackAI) plus declared preconditions across 22 existing tools. New surface is a minor bump under semver; 1.3.x is for the patches that have been going out.Why this is its own PR
Review feedback on #379: a version bump doesn't belong in a feature PR, and repo convention is a separate bump PR. #379 has been reverted to
1.3.2accordingly and stays there.One sequencing consequence worth knowing
1.4.0-beta.1…beta.3are already published, derived from apackage.jsonthat said1.4.0. With #379 back on1.3.2, a Beta Release run from that branch would now compute1.3.1-beta.1/1.3.2-beta.1andnpm publish --tag betawould move thebetadist-tag backwards, since it repoints unconditionally with no version-ordering check.So: merge this before cutting any further beta from #379. The betas so far were published from a throwaway drop branch carrying the bumped version, precisely to avoid that.
Also for awareness: the
betatag currently points at1.4.0-beta.3(this feature), while a separate1.5.0-beta.*line also exists. Worth agreeing who ownsbetabefore the next publish either way.Risk
None at runtime — three version strings, no code.
npm run buildis unaffected.