FLEXY-0000 bump the workspace version to 7.1.3 - #1172
Merged
Merged
Conversation
main was left at 7.1.2 even though 7.1.3 was published, because the steps that commit lerna's bump back to the repository were disabled at the time. A public release reads lerna.json to decide the next version, so a patch release from 7.1.2 would produce 7.1.3 again and npm would reject it as an already-published version for the eleven packages that did publish. Bumped by hand rather than with `lerna version`, since that command also tags and commits, and these versions are already live on npm. The result is the same shape as lerna's own bump commit 970b13c (v7.1.2): 14 files, 65 insertions and 65 deletions, with identical per-file counts. lerna.json and all twelve packages/*/package.json version fields the twenty internal cross-dependency pins, which --exact keeps exact the twelve workspace entries in package-lock.json @twilio/flex-ui stays at "^2"; it is not one of ours. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
shwet2407
approved these changes
Sep 30, 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
2 participants
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.
Why
mainstill says7.1.2inlerna.jsoneven though7.1.3was published, because thepublish.ymlsteps that commit lerna's bump back to the repository (Commit Version,Create PR for version) were disabled at the time.That matters for the next release.
bin/publishreadslerna.jsonto decide the next version, and the public path only accepts a bump level —patch,minorormajor— never an exact version. So a patch release from7.1.2would compute7.1.3again, andnpm publishwould reject it as an already-published version for the eleven packages that did publish. Bumpingmainto7.1.3makes the next patch release land on7.1.4.What changed
lerna.jsonand all twelvepackages/*/package.jsonversion fields--exactkeeps at the exact versionpackage-lock.json@twilio/flex-uistays at"^2"— it is not one of ours. No Artifactory URLs in the lockfile.Verification
Bumped by hand rather than with
lerna version, since that command also tags and commits and these versions are already live on npm.The result matches lerna's own bump commit
970b13c5(v7.1.2) exactly in shape: 14 files, 65 insertions, 65 deletions, identical per-file line counts and 13 lockfile hunks. With the version number normalised, the set of changed lines is identical in both.npm run lintpasses via the pre-commit hook (0 errors).Note
This does not re-enable
Commit Version/Create PR for version, so the next public release will drift again unless those are restored first.🤖 Generated with Claude Code