chore(shared): fix the release config for breaking changes

[designcode]

Note

Medium Risk
Changes semantic-release commit analysis rules, which can alter versioning/publishing behavior across packages. Risk is mainly around missed or unexpected releases if breaking-change commits are scoped differently than assumed.

Overview
Updates release.config.base.cjs semantic-release releaseRules to explicitly ignore breaking-change commits whose scope does not match the current package.

This prevents a breaking change in another package’s scope from triggering a major release for this package.

^{Reviewed by Cursor Bugbot for commit 4cba432. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds a missing catch-all releaseRules entry so that breaking changes scoped to other packages (e.g. feat(cli)!:) don't accidentally trigger a major version bump for the current package. The new rule { scope: \!(${scope})`, breaking: true, release: false }mirrors the already-existing positive-scope rule{ scope, breaking: true, release: 'major' }` and is consistent with the rest of the negation block.

Confidence Score: 5/5

Safe to merge — the change is a one-line addition that completes an existing symmetrical pattern with no side effects.

No P0 or P1 issues found. The rule is logically correct, mirrors the established pattern for scope-negation rules, and all four package-level configs delegate to this base, so the fix propagates consistently across the monorepo.

No files require special attention.

Vulnerabilities

No security concerns identified.

Important Files Changed

Filename	Overview
release.config.base.cjs	Adds a negation catch-all rule so breaking changes from other package scopes don't trigger a major release in the current package; mirrors the existing positive-scope pattern correctly.

_{Reviews (1): Last reviewed commit: "chore(shared): fix the release config fo..." | Re-trigger Greptile}

[github-actions]

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀