fix: sync lockfile to match package

[alexmercerpo]

Summary by CodeRabbit

• Chores
  • Enhanced release automation workflows to ensure consistency between package versions and dependency information during release operations.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 50516b8a-27c2-4442-889c-7ab59c2df105

📥 Commits

Reviewing files that changed from the base of the PR and between bd00b51 and 7a94398.

📒 Files selected for processing (2)

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

---

📝 Walkthrough

Walkthrough

Two CI release workflows gain a "Sync lockfile to bumped versions" step that runs yarn install --no-immutable after package version bumps. In create-release-branch.yml the step is unconditional; in publish-release.yml it is guarded by inputs.dry_run != true.

Changes

Lockfile sync in release workflows

Layer / File(s)	Summary
Lockfile regeneration steps .github/workflows/create-release-branch.yml, .github/workflows/publish-release.yml	Adds a yarn install --no-immutable step after version bumps in both workflows. The create-release-branch.yml step runs unconditionally; the publish-release.yml step is gated on inputs.dry_run != true.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• agentfront/enclave#6: Modifies create-release-branch.yml around the same version-bump/dependency update logic that this PR's new lockfile sync step follows.
• agentfront/enclave#10: Switches the post-bump release-branch workflow logic to Nx Release in create-release-branch.yml, directly adjacent to where this PR inserts the lockfile sync step.
• agentfront/enclave#54: Introduced the demo-app @enclave-vm/* dependency version bump in publish-release.yml that this PR's new lockfile sync step follows.

Poem

🐇 Hippity-hop, the lockfile must match,
After the bumps, we run the right batch.
--no-immutable lets the lock breathe free,
No stale old entries to bother thee!
With a twitch of my nose, the CI stays neat~ 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main changes: syncing lockfiles to match package versions in release workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-export

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Cherry-pick Created

A cherry-pick PR to main has been automatically created.

Please review and merge if this change should also be in main.

If the cherry-pick is not needed, close the PR.