ci: reinstate Release workflow with OIDC trusted publishing - #29
Merged
Conversation
Restores automated publishing removed in 7551d28. On merge to main it consumes pending changesets, bumps the version, and publishes to npm over OIDC trusted publishing (no token secret). Standardizes CONTRIBUTING on yarn to stop the lockfile drift that broke the previous workflow, and documents the changeset flow plus a break-glass manual path.
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.
Restores the automated publish pipeline that was removed in
7551d28("we publish manually"), this time tokenless.What it does
On merge to
main,.github/workflows/release.ymlconsumes any pending changesets, bumps the version + changelog, and publishes@thatopen/servicesto npm via OIDC trusted publishing — noNPM_TOKENsecret. Anyone can cut a release by adding a changeset in a PR; no one holds a token.Why the old one broke
It ran
yarn install --frozen-lockfileagainst a lockfile that had drifted because the repo mixed npm and yarn. This standardizesCONTRIBUTINGon yarn (the committed lockfile + CI already use it) to stop the drift.Changes
.github/workflows/release.yml— restored,id-token: write, upgrades npm to an OIDC-capable version, no token secretCONTRIBUTING.md— setup/build standardized on yarn; publishing section documents the changeset → merge → CI-publishes flow, with a break-glass manual pathRequires before it can publish
A trusted publisher configured on npm for
@thatopen/services: GitHub Actions, orgThatOpen, repoplatform_services, workflowrelease.yml.On merge
A
get-avatar.mdchangeset is already onmain, so the first run will publish a minor bump (0.3.16 → 0.4.0) shippingPlatformClient.getAvatar.