ci: add release workflow (npm trusted publishing + GitHub Release)#6
Merged
Conversation
Triggers on push of any v*-tag. Runs build + tests, then: - npm publish --provenance --access=public (via OIDC, no secret token) - Creates a GitHub Release at the tag with auto-generated notes Requires npm Trusted Publishing to be configured separately at https://www.npmjs.com/package/flappie-api/access (one-time setup, linked to ooswald/flappie-api + workflow file release.yml). Until that's done the publish step fails - the rest still runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
.github/workflows/release.ymlthat triggers on anyv*tag push and:npm ci, build, testsnpm publish --provenance --access=publicvia OIDC trusted publishing — no token in CIsoftprops/action-gh-release@v2)Required follow-up (one-time setup)
Configure npm Trusted Publishing for the package:
ooswald, Repository:flappie-api, Workflow filename:release.yml, Environment: (empty)Until that's done, the publish step on this workflow will fail with an OIDC error. The rest (build + test) still runs, so this is safe to merge.
How releases work after this
No more browser passkey prompts; no npm token in any secret. The OIDC trust is scoped to this repo + this workflow file.