Republish all packages with build provenance - #41
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: d4e7077 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
What
Adds a
patchchangeset for all four publishable packages:@kin0992/oxc-config@kin0992/skills@kin0992/tsconfig@kin0992/vitest-configNo functional changes — this exists to cut a fresh release so the next publish attaches signed provenance (npm Trusted Publishing / OIDC), which the current versions lack.
Release flow
Merging this PR triggers the release workflow, which opens a "Version Packages" PR bumping each package by a patch. Merging that PR publishes to npmjs.org with provenance.
Trusted Publishing must already be configured on npmjs.org for each of the four packages (GitHub Actions →
kin0992/dev-toolkit→release.yml), and PR #40 must be merged first — otherwise the publish step fails auth. Provenance attaches on this publish; existing versions can't be back-filled.🤖 Generated with Claude Code