chore: bump version to 1.2.25#330
Merged
Merged
Conversation
… server.json Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ruturaj-browserstack
approved these changes
Jun 26, 2026
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
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.
Version bump 1.2.24 → 1.2.25 ahead of the next npm release, per the manual-bump release flow.
Updates the version in all three files:
package.json→versionpackage-lock.json→ top-levelversionand the rootpackages.""entryserver.json→packages[].version(top-levelversionstays1.0.0, it's the schema version)Only the four version lines change; no code changes.
This bump is what the
Release New Versionworkflow publishes frommain. For the release to include the custom-template /listTestCaseTemplateswork, merge #328 first, then this bump, then dispatch the release. If #328 isn't inmainwhen the release runs, 1.2.25 will ship without it.