General: Bump version to 2.16.2 for all components - #2076
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request updates nine client package manifests from version ChangesClient package version alignment
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized patch-version update across the client packages with no actionable merge-blocking risk remaining after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Bumps the client version from
2.16.1to2.16.2(one patch version) across all Module Federationpackages in preparation for the next patch release.
Details
Updated the
versionfield from2.16.1to2.16.2in all nine clientpackage.jsonfiles, so theworkspace root and every remote stay in lockstep:
clients/package.json(prompt-module-federationworkspace root)clients/core/package.jsonclients/assessment_component/package.jsonclients/certificate_component/package.jsonclients/example_component/package.jsonclients/interview_component/package.jsonclients/matching_component/package.jsonclients/self_team_allocation_component/package.jsonclients/team_allocation_component/package.jsonNo other files change. A repo-wide search for the
2.16.1string matches only these nineversionfields (the remaining hits are unrelated
is-core-module@2.16.1entries indocs/yarn.lock), so nosource, configuration, or documentation reference needs updating.
clients/yarn.lockdoes not recordworkspace versions and therefore needs no regeneration.
The bump is kept as a single commit on purpose: the nine files have to move together, and splitting
them would leave intermediate commits where the workspace root and the remotes disagree.
Reason / Link to issue
The release tag is derived from the
versionfield inclients/core/package.json, so the bump has toland before the release is drafted. A patch bump reflects that the work merged since
2.16.1containsno new features or breaking changes.
How to Test
grep -H '"version"' clients/package.json clients/*/package.jsonand confirm all nine filesreport
2.16.2.make lintand confirm it passes.PR Checklist
Summary by CodeRabbit