ci: do not publish auth-helpers-* #146
Merged
Conversation
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
staaldraad
approved these changes
Nov 27, 2025
mandarini
force-pushed
the
ci/release-auth-helpers
branch
2 times, most recently
from
f7396f9 to
8a9dbc4
Compare
mandarini
force-pushed
the
ci/release-auth-helpers
branch
from
07044ff to
9485101
Compare
mandarini
force-pushed
the
ci/release-auth-helpers
branch
from
bbef35c to
982ef8c
Compare
mandarini
changed the title
mandarini
force-pushed
the
ci/release-auth-helpers
branch
from
d783bcd to
f380616
Compare
mandarini
force-pushed
the
ci/release-auth-helpers
branch
from
f380616 to
6b8bb0d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
@supabase/auth-helpers-*anymore.A final version of
@supabase/auth-helpers-*was released,0.15.0for all, that has@supabase/ssrunder the hood, and the README in npm tells them to use@supabase/ssrinstead.No reason to keep publishing. Also, we want these packages to show as deprecated, and every new release undeprecates them. There's no simple way to deprecate them from CI, because it needs 2FA.