build(deps): bump actions/checkout from 6.0.2 to 6.0.3#245
Merged
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 6.0.3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@de0fac2...df4cb1c) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
mandarini
approved these changes
Jun 5, 2026
mandarini
added a commit
that referenced
this pull request
Jun 9, 2026
## Summary - Re-adds an explicit npm install before the publish step so the workflow runs on **npm 11.5.2** (the version that supports OIDC trusted-publisher exchange) instead of Node 22's bundled npm 10.9.x. - Adds a multi-line comment in the workflow explaining the dependency, so the line is not deleted again. ## Background The release pipeline has been silently broken since #221 (May 12). That PR removed `corepack enable npm && corepack prepare npm@11 --activate` with the claim "no longer needed", but `actions/setup-node@v6.4.0` does **not** upgrade npm — Node 22 ships with npm 10.9.x. npm only learned how to do OIDC trusted-publisher exchange in **11.5.1**. On npm 10, `npm publish --provenance` signs the provenance via sigstore (which works because it uses the GitHub OIDC token directly), then sends the bogus `.npmrc` placeholder `XXXXX-XXXXX-XXXXX-XXXXX` as the bearer token to the registry. The registry returns `404 Not Found - PUT https://registry.npmjs.org/@supabase%2fssr` (npm registry returns 404 for unauthenticated PUTs to avoid leaking which packages exist). The repo has **no `NPM_TOKEN` secret** configured anywhere — by design, per #221's hardening posture. Auth is OIDC-only via the trusted-publisher binding on npmjs.com. Re-adding a token would weaken that posture, so the fix is to ensure the npm CLI is new enough to use OIDC. ## Why this went undetected Between #221's merge (May 12) and #240's merge (June 4), every release run was for a `chore: update @supabase/supabase-js` commit. Those have no pending release-please PR, so the workflow's version-determination step took the `skip=true` branch and never attempted to publish. The first publish attempt on npm 10 — #240's merge on June 4 — failed with E404, as did the two release runs after it (#245, #244). Failed runs: - [27136548767](https://github.com/supabase/ssr/actions/runs/27136548767) — PR #244 ("release 0.11.0") merge, tried to publish `0.12.0-rc.118` - [27008002122](https://github.com/supabase/ssr/actions/runs/27008002122) — PR #245 merge - [26949675017](https://github.com/supabase/ssr/actions/runs/26949675017) — PR #240 merge, tried to publish `0.11.0-rc.117` Last successful publish: `v0.10.3` on May 7 (run [25509681243](https://github.com/supabase/ssr/actions/runs/25509681243)), which ran on npm 11 via the corepack line that #221 removed. 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.
Bumps actions/checkout from 6.0.2 to 6.0.3.
Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
df4cb1cUpdate changelog for v6.0.3 (#2446)1cce339Fix checkout init for SHA-256 repositories (#2439)900f221fix: expand merge commit SHA regex and add SHA-256 test cases (#2414)0c366fdUpdate changelog (#2357)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)