ci: link each release's npm publish as artifact metadata - #916
Merged
Conversation
… linked-artifacts page
Adds a step to the attest-release-artifacts job that records each released package's npm
registry location via POST /orgs/{org}/artifacts/metadata/storage-record, using the same
sha256 digest actions/attest just signed for build provenance.
GITHUB_TOKEN has no equivalent permission for this org-level endpoint, so the step mints a
token from the documents-js GitHub App the release job already uses for its own elevated
pushes, scoped down to only the artifact-metadata permission this one call needs.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Adds a step to the attest-release-artifacts job that records each released package's npm registry location via
POST /orgs/{org}/artifacts/metadata/storage-record, using the same sha256 digestactions/attestjust signed for build provenance — so it shows up on the org's own linked-artifacts page (Packages tab) pointing at the real npm tarball.GITHUB_TOKENhas no permission for this org-level endpoint (confirmed via a live test call with a classic token carryingadmin:org, which still 404'd — this genuinely needs the newerartifact-metadataApp-style permission, not any classic OAuth scope). The step mints a token from thedocuments-jsGitHub App the release job already uses for its own elevated pushes, scoped down withpermission-artifact-metadata: writeto just what this one call needs rather than inheriting the App's other permissions.Requires the
documents-jsApp's installation on ExaDev to already carry theArtifact metadatapermission — confirmed live via the API before opening this PR.