Repository navigation
ci: publish to npm from a tag push with provenance and attestation - #31
Merged
Merged
Conversation
The Release workflow runs on a v<version> tag: it reruns the test workflow, checks the tag matches packages/map-views/package.json, publishes the packed library through npm trusted publishing with provenance, attests the tarball and attaches it to a GitHub release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Xphpf9ejzNMsN83ehiZnu
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
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.
Requested by Rog · project thread
What
Pushing a
v<major>.<minor>.<patch>tag (the/releaseskill's step 2) runs a new Release workflow:test.ymlis now alsoworkflow_call).packages/map-views/package.json.packages/map-views(never the private workspace root), attests the tarball.npm publish --provenancethrough npm trusted publishing (OIDC, no token).The
/releaseskill and AGENTS.md now describe watching the workflow instead of runningnpm publishlocally.Setup needed before the first tagged release
structured-context-map-views→ Settings → Trusted publishing → GitHub Actions: ownermindsocket, repostructured-context-map-views, workflowrelease.yml, environmentnpm.v*, required reviewers on thenpmenvironment.Not verified
Can't run before it's on
mainand trusted publishing is configured; YAML parses and lint passes.Generated by Claude Code