fix(shared): release sequentially

[designcode]

Note

Update release script to run multi-semantic-release with --sequential-init for sequential releases.

^{Written by Cursor Bugbot for commit 9336652. This will update automatically on new commits. Configure here.}

[greptile-apps]

Greptile Overview

Greptile Summary

Added --sequential-init flag to the multi-semantic-release command to ensure packages are released sequentially rather than in parallel.

• Addresses potential race conditions or dependency ordering issues during the release process
• Single-line change with minimal risk

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change adds a single configuration flag to fix a known issue with parallel release execution. The flag is a documented feature of multi-semantic-release that controls initialization behavior. No logic changes, no syntax issues, and the flag has no negative side effects.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
package.json	5/5	Added --sequential-init flag to multi-semantic-release command to fix release timing issues

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[github-actions]

🎉 This PR is included in version 1.0.7 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.1.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 2.10.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀