chore(release): v0.24.3 - #310
Merged
Merged
Conversation
Patch: nothing that ships changed. The only commit since v0.24.2 is the switch back to trusted publishing (#309), and .github is not in the package's `files`. Cut to prove that switch. Nothing in the repository can check whether the trusted publisher is registered on npmjs.com — the registry does not expose it — and a dispatch run cannot reach the publish while 0.24.2 is the current version. A release is the only thing that exercises the OIDC exchange. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan92 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 42
…and 42 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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
1 participant
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.
Summary
Patch: nothing that ships changed. The only commit since v0.24.2 is the switch back to trusted publishing (#309), and
.githubis not in the package'sfileslist — the tarball is unchanged apart from the version field.Why cut it
To prove that switch. Nothing in the repo can check whether the trusted publisher is registered on npmjs.com — the registry does not expose that config, which I checked — and a dispatch run cannot reach the publish step while 0.24.2 is the current version, because the skip guard stops first. A release is the only thing that exercises the OIDC exchange.
Two outcomes, both informative:
E404 … could not be found or you do not have permission, which the workflow header now explains. Nothing partial gets published and the version is not burned.Verification
moshcode --versionreports 0.24.3repositoryfield (added in chore(release): v0.24.2 — add the repository field provenance requires #308, which fixed the v0.24.1 E422) is intact, so provenance validation has something to match🤖 Generated with Claude Code