Skip to content

chore(main): release 0.11.0#244

Merged
mandarini merged 1 commit into
mainfrom
release-please--branches--main--components--ssr
Jun 8, 2026
Merged

chore(main): release 0.11.0#244
mandarini merged 1 commit into
mainfrom
release-please--branches--main--components--ssr

Conversation

@supabase-releaser

@supabase-releaser supabase-releaser Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.11.0 (2026-06-05)

Features

  • cookies: add clearAuthCookiesAtScopes migration helper (#240) (4e47249)

This PR was generated with Release Please. See documentation.

@supabase-releaser supabase-releaser Bot force-pushed the release-please--branches--main--components--ssr branch from a61ef17 to 47d8b42 Compare June 5, 2026 09:51
@mandarini mandarini merged commit dd766c4 into main Jun 8, 2026
4 checks passed
@mandarini mandarini deleted the release-please--branches--main--components--ssr branch June 8, 2026 12:08
@supabase-releaser

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant