OIDC trusted publishing + update @malloydata deps to 0.0.396#200
Merged
Conversation
Both publish jobs (publish-next, publish-latest) now authenticate to npm with GitHub Actions OIDC trusted publishing instead of the static NPM_TOKEN secret: - add id-token: write to both jobs - upgrade the runner npm to >=11.5.1 (OIDC publish requirement) - drop registry-url from setup-node (avoids an empty-token .npmrc that would shadow OIDC) and remove NODE_AUTH_TOKEN @malloydata/cli is registered on npmjs.com with malloydata/malloy-cli + npm-publish.yml as its trusted publisher, covering both jobs. The publish-latest GitHub App token stays; it's used for the git push, not npm auth.
npm run malloy-update (latest dist-tag) to pick up the 0.0.396 core release.
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.
OIDC trusted publishing
Migrates both publish jobs in
npm-publish.ymlfrom the staticNPM_TOKENto GitHub Actions OIDC trusted publishing (matching the mainmalloydata/malloyrepo):id-token: writeonpublish-nextandpublish-latestregistry-url(avoids an empty-token.npmrcshadowing OIDC) and removedNODE_AUTH_TOKEN@malloydata/cliis registered on npmjs.com withmalloydata/malloy-cli+npm-publish.ymlas its trusted publisher, so both jobs are covered. Thepublish-latestGitHub App token is unchanged — it's for the git push, not npm auth. OIDC also enables provenance automatically; the package already has arepositoryfield, so no provenance issue.Dependency bump
npm run malloy-updateto pick up the 0.0.396 core release (all 8@malloydata/*deps).Verifying
publish-nextOIDC path runs automatically on merge (publishes@next).publish-latestworkflow has adry_runinput that exercises the OIDC path without publishing.