fix: refresh yarn.lock to match bumped versions after release versioning (#493)

[frontegg-david]

• docs: update documentation for v1.2.0 features and clarify unsupported functionalities

• fix: refresh yarn.lock to match bumped versions after release versioning

Summary by CodeRabbit

• Chores
  • Improved CI/CD release workflows to enhance dependency synchronization. Updated build and publish processes now automatically synchronize dependency lockfiles with updated package configurations, ensuring consistency between package manifests and lockfiles during version updates. This reduces potential build failures and improves overall release reliability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 85e75b00-c1b7-4700-9c3e-3f7866606af8

📥 Commits

Reviewing files that changed from the base of the PR and between 365aac8 and 329f086.

📒 Files selected for processing (2)

• .github/workflows/create-release-branch.yml
• .github/workflows/publish-release.yml

---

📝 Walkthrough

Walkthrough

Two GitHub Actions workflow files (create-release-branch.yml and publish-release.yml) each receive a new step that runs yarn install --mode=update-lockfile after the internal @frontmcp/* version pins are rewritten, ensuring yarn.lock stays consistent before any subsequent --immutable install steps.

Changes

Lockfile Refresh in Release Workflows

Layer / File(s)	Summary
yarn.lock refresh steps in both release workflows .github/workflows/create-release-branch.yml, .github/workflows/publish-release.yml	Adds a "Refresh yarn.lock to match bumped versions" step to each workflow's release-preparation job, running yarn install --mode=update-lockfile after @frontmcp/* version pins are normalized so the lockfile reflects the updated exact versions before commit.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Manual cherry-pick needed: fix: refresh yarn.lock to match bumped versions after release versioning #494: This PR directly implements the fix described in that issue by adding yarn install --mode=update-lockfile steps to refresh yarn.lock after internal dependency version normalization during release workflows.

Possibly related PRs

• agentfront/frontmcp#358: Directly related — this PR extends the publish-release.yml manifest normalization logic introduced in PR #358 by adding the lockfile refresh step that follows the @frontmcp/* version rewriting.

Poem

🐇 Hop, hop, the lockfile was stale,
Versions bumped but yarn would wail!
Now --mode=update-lockfile runs,
Saving the release from broken guns.
Immutable installs, rejoice and cheer —
The bunny fixed it, crystal clear! 🎉

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cherry-pick-pr-493

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Performance Test Results

Status: ✅ All tests passed

Summary

Project	Tests	Passed	Warnings	Failed	Leaks
✅ demo-e2e-agents	4	4	0	0	0
✅ demo-e2e-cache	11	11	0	0	0
✅ demo-e2e-codecall	4	4	0	0	0
✅ demo-e2e-config	4	4	0	0	0
✅ demo-e2e-direct	3	3	0	0	0
✅ demo-e2e-elicitation	1	1	0	0	0
✅ demo-e2e-errors	4	4	0	0	0
✅ demo-e2e-hooks	3	3	0	0	0
✅ demo-e2e-multiapp	4	4	0	0	0
✅ demo-e2e-notifications	3	3	0	0	0
✅ demo-e2e-openapi	2	2	0	0	0
✅ demo-e2e-providers	4	4	0	0	0
✅ demo-e2e-public	4	4	0	0	0
✅ demo-e2e-redis	15	15	0	0	0
✅ demo-e2e-remember	4	4	0	0	0
✅ demo-e2e-remote	5	5	0	0	0
✅ demo-e2e-serverless	2	2	0	0	0
✅ demo-e2e-skills	15	15	0	0	0
✅ demo-e2e-standalone	2	2	0	0	0
✅ demo-e2e-transport-recreation	3	3	0	0	0
✅ demo-e2e-ui	4	4	0	0	0

Total: 101 tests across 21 projects

📊 View full report in workflow run

---

Generated at: 2026-06-21T17:20:15.549Z
Commit: 5d6aea75