chore: version packages#103
Merged
Merged
Conversation
commit: |
Contributor
API Changes Report
Summary
No API Changes DetectedAll packages have stable APIs with no detected changes. Report generated by Break Check |
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.4.0
Minor Changes
#101
1860598Thanks @jacekradko! - Skip reasons for subpaths API Extractor cannot snapshot are now classifiedinto actionable messages instead of echoing AE's raw InternalError text. An
ambient entry
.d.ts(no top-level import or export) is reported as a surfaceAE can never analyze, and an unresolvable type name in the shipped
declarations is reported as likely-broken published types; both point at
ignoreSubpathsas the acknowledgment path and keep the original AE firstline for traceability. Unrecognized messages pass through with only the
"software defect" boilerplate stripped.
#99
4c81537Thanks @jacekradko! - A reference repair is now reported non-breaking (issue #98). When a breakingmodification's only diff is swapping module specifiers consumers could not
resolve (export-blocked, e.g.
@clerk/shared/_chunks/index-Cr_OtBLqunder"./_chunks/*": null, or chunk-shaped with the dependency unlocatable) forspecifiers that provably resolve against the dependency's
exports, the changeis deterministically downgraded and tagged as a repaired reference in the
report. The old reference errored (TS2307) or degraded to
anydownstream, sofixing it cannot break anyone. The check is fail-closed: any difference beyond
the specifier/alias swap, or an introduced specifier that does not provably
resolve, keeps the change breaking. Opt out with
downgradeRepairedReferences: false.The AI reviewer now also receives deterministic exports-map verdicts
(
referenceResolutions) for every specifier a signature drops or introduces,instead of guessing resolvability from path shapes, and cannot escalate a
deterministically repaired change back to breaking (recorded as
ai-suggested-escalation, mirroring the downgrade refusal for unresolvablereferences).