- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 9
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: supabase/ssr
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.4.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: supabase/ssr
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.5.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 6 files changed
- 5 contributors
Commits on Jul 3, 2024
-
fix: set cookies when mfa challenge is verified (#27)
## What kind of change does this PR introduce? Currently, create server client doesn't seem to set cookies when MFA Challenge is verified
Configuration menu - View commit details
-
Copy full SHA for c217f53 - Browse repository at this point
Copy the full SHA c217f53View commit details -
fix: update conventional commits ci to use main instead of master (#31)
## What kind of change does this PR introduce? As per title
Configuration menu - View commit details
-
Copy full SHA for bebce89 - Browse repository at this point
Copy the full SHA bebce89View commit details -
fix: set cookies for password recovery event (#32)
## What kind of change does this PR introduce? Bug fix ## What is the current behavior? When resetting a user's password with an email template which has a URL defining the `type` value as `recovery`, and using the `verifyOtp` method to process the token_hash and type, the SSR server client's `onAuthStateChange` function does not recognize the `PASSWORD_RECOVERY` event that verifyOtp fires. This prevents the code [here](https://github.com/supabase/ssr/blob/main/src/createServerClient.ts#L199-L205) from running; resulting in the new session not being saved to cookies, and the user is not considered logged in. Fixes #21 ## What is the new behavior? User is logged in. ## Additional context Replaces PR #24 Co-authored-by: Jason Creviston <jason@malynium.com>
Configuration menu - View commit details
-
Copy full SHA for 7dc1837 - Browse repository at this point
Copy the full SHA 7dc1837View commit details
Commits on Jul 4, 2024
-
feat: update CI so it runs on release as well (#33)
## What kind of change does this PR introduce? so that we can unblock v0.4.1. Referencing the Auth workflow: https://github.com/supabase/auth/blob/master/.github/workflows/test.yml
Configuration menu - View commit details
-
Copy full SHA for 4517996 - Browse repository at this point
Copy the full SHA 4517996View commit details
Commits on Jul 30, 2024
-
ci: remove CHANGELOG.md from prettier check (#43)
Since `CHANGELOG.md` is maintained by Release Please, ignoring prettier on it.
Configuration menu - View commit details
-
Copy full SHA for 36d850e - Browse repository at this point
Copy the full SHA 36d850eView commit details -
ci: fix
latest
npm dist tag when patching versions (#45)If a specific patch is made on a release branch, it will always use the `patched` NPM dist tag. This also checks if the patched release branch is the latest release branch to use the `latest` NPM dist tag.
Configuration menu - View commit details
-
Copy full SHA for ae6af1d - Browse repository at this point
Copy the full SHA ae6af1dView commit details
Commits on Aug 19, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9d0e859 - Browse repository at this point
Copy the full SHA 9d0e859View commit details -
Configuration menu - View commit details
-
Copy full SHA for 51d5a43 - Browse repository at this point
Copy the full SHA 51d5a43View commit details -
chore(main): release 0.5.0 (#28)
🤖 I have created a release *beep* *boop* --- ## [0.5.0](v0.4.0...v0.5.0) (2024-08-19) ### Features * update CI so it runs on release as well ([#33](#33)) ([4517996](4517996)) ### Bug Fixes * re-apply update CI so it runs on release as well ([#49](#49)) ([51d5a43](51d5a43)) * revert "update CI so it runs on release as well" ([#44](#44)) ([9d0e859](9d0e859)) * set cookies for password recovery event ([#32](#32)) ([7dc1837](7dc1837)) * set cookies when mfa challenge is verified ([#27](#27)) ([c217f53](c217f53)) * update conventional commits ci to use main instead of master ([#31](#31)) ([bebce89](bebce89)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 9cd6813 - Browse repository at this point
Copy the full SHA 9cd6813View commit details
There are no files selected for viewing