chore: release 0.0.4#18
Merged
Merged
Conversation
Bump package version 0.0.3 -> 0.0.4 (0.0.3 is already on npm) and sync the release-please manifest to 0.0.4 so version state matches the registry. Enables publishing the merged skills-alignment changes via the trusted publish workflow. Co-authored-by: Cursor <cursoragent@cursor.com>
YoniMelki
approved these changes
Jun 23, 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.
Summary
Prepare the first npm release of the new skills-alignment architecture.
package.json0.0.3 → 0.0.4(0.0.3is already published on npm; a republish would fail)..release-please-manifest.json0.0.1 → 0.0.4so release-please's version state matches the registry (it was proposing a bogus0.0.2in chore(main): release 0.0.2 #17).Why
The merged skills work (#16) isn't on npm yet. The automated
publish.ymlpath fails withENEEDAUTHbecause the npm trusted publisher is bound topublish-as-is.yml(verified via the SLSA provenance of0.0.3, the only OIDC publish to date).Publish procedure (after merge)
Run the "Publish public Package version" workflow (
publish-as-is.yml) frommain→ publishes0.0.4@latestvia OIDC (trusted publisher matches this workflow).Notes
publish.ymlautomation (a possible later improvement for hands-off releases).Made with Cursor