chore: version packages#106
Merged
Merged
Conversation
Contributor
API Changes Report
Summary
No API Changes DetectedAll packages have stable APIs with no detected changes. Report generated by Break Check |
commit: |
jacekradko
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@clerk/break-check@0.5.0
Minor Changes
3f376e1Thanks @jacekradko! - Support package-scopedignoreSubpathsentries. A bare entry still applies to every configured package; an entry prefixed with a package name and#(the same separatoracknowledgedChangesuses) ignores the subpath only in matching packages, e.g."@clerk/astro#./env". Globs are accepted on both sides ("@clerk/*#./internal"), which goes beyondacknowledgedChanges, whose package part is matched exactly. Skip-reason warnings for unsnapshotable subpaths now name the exact scoped entry to copy. Entries starting with.keep their historical meaning byte-for-byte; the only reinterpreted shape is a non-dot entry containing#(e.g.**#./env), which previously matched a literal#inside an exports key and is now read as a scoped entry.