Repository navigation
chore: bump version to v2.7.1 - #176
Closed
shubham-vapiai wants to merge 1 commit into
Closed
shubham-vapiai wants to merge 1 commit into
shubham-vapiai wants to merge 1 commit into
Conversation
shubham-vapiai
enabled auto-merge (squash)
September 18, 2026 18:25
auto-merge was automatically disabled
September 18, 2026 18:46
Pull request was closed
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.
The v2.7.1 release failed verification because the tagged commit still declared version 2.7.0. Bump package.json and both package-lock.json version fields to 2.7.1 so a merged release PR satisfies the workflow's version-bump requirement.
Validation: npm ci, npm run build, and npm test -- --runInBand passed (61 tests across 2 suites). Verified all three version fields equal 2.7.1 and the diff contains only the two package files.
This PR does not move the existing v2.7.1 tag or republish the release; that remains a separate step after merge.