-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spelling error: posession -> possession #1682
Comments
J0
added a commit
that referenced
this issue
Jul 30, 2024
## What kind of change does this PR introduce? fix #1682
J0
pushed a commit
that referenced
this issue
Jul 31, 2024
🤖 I have created a release *beep* *boop* --- ## [2.158.0](v2.157.0...v2.158.0) (2024-07-31) ### Features * add hook log entry with `run_hook` action ([#1684](#1684)) ([46491b8](46491b8)) * MFA (Phone) ([#1668](#1668)) ([ae091aa](ae091aa)) ### Bug Fixes * maintain backward compatibility for asymmetric JWTs ([#1690](#1690)) ([0ad1402](0ad1402)) * MFA NewFactor to default to creating unverfied factors ([#1692](#1692)) ([3d448fa](3d448fa)) * minor spelling errors ([#1688](#1688)) ([6aca52b](6aca52b)), closes [#1682](#1682) * treat `GOTRUE_MFA_ENABLED` as meaning TOTP enabled on enroll and verify ([#1694](#1694)) ([8015251](8015251)) * update mfa phone migration to be idempotent ([#1687](#1687)) ([fdff1e7](fdff1e7)) --- 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>
uxodb
pushed a commit
to uxodb/auth
that referenced
this issue
Nov 13, 2024
## What kind of change does this PR introduce? fix supabase#1682
uxodb
pushed a commit
to uxodb/auth
that referenced
this issue
Nov 13, 2024
🤖 I have created a release *beep* *boop* --- ## [2.158.0](supabase/auth@v2.157.0...v2.158.0) (2024-07-31) ### Features * add hook log entry with `run_hook` action ([supabase#1684](supabase#1684)) ([46491b8](supabase@46491b8)) * MFA (Phone) ([supabase#1668](supabase#1668)) ([ae091aa](supabase@ae091aa)) ### Bug Fixes * maintain backward compatibility for asymmetric JWTs ([supabase#1690](supabase#1690)) ([0ad1402](supabase@0ad1402)) * MFA NewFactor to default to creating unverfied factors ([supabase#1692](supabase#1692)) ([3d448fa](supabase@3d448fa)) * minor spelling errors ([supabase#1688](supabase#1688)) ([6aca52b](supabase@6aca52b)), closes [supabase#1682](supabase#1682) * treat `GOTRUE_MFA_ENABLED` as meaning TOTP enabled on enroll and verify ([supabase#1694](supabase#1694)) ([8015251](supabase@8015251)) * update mfa phone migration to be idempotent ([supabase#1687](supabase#1687)) ([fdff1e7](supabase@fdff1e7)) --- 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>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this issue
Nov 13, 2024
## What kind of change does this PR introduce? fix supabase#1682
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this issue
Nov 13, 2024
🤖 I have created a release *beep* *boop* --- ## [2.158.0](supabase/auth@v2.157.0...v2.158.0) (2024-07-31) ### Features * add hook log entry with `run_hook` action ([supabase#1684](supabase#1684)) ([46491b8](supabase@46491b8)) * MFA (Phone) ([supabase#1668](supabase#1668)) ([ae091aa](supabase@ae091aa)) ### Bug Fixes * maintain backward compatibility for asymmetric JWTs ([supabase#1690](supabase#1690)) ([0ad1402](supabase@0ad1402)) * MFA NewFactor to default to creating unverfied factors ([supabase#1692](supabase#1692)) ([3d448fa](supabase@3d448fa)) * minor spelling errors ([supabase#1688](supabase#1688)) ([6aca52b](supabase@6aca52b)), closes [supabase#1682](supabase#1682) * treat `GOTRUE_MFA_ENABLED` as meaning TOTP enabled on enroll and verify ([supabase#1694](supabase#1694)) ([8015251](supabase@8015251)) * update mfa phone migration to be idempotent ([supabase#1687](supabase#1687)) ([fdff1e7](supabase@fdff1e7)) --- 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>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this issue
Nov 15, 2024
## What kind of change does this PR introduce? fix supabase#1682
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this issue
Nov 15, 2024
🤖 I have created a release *beep* *boop* --- ## [2.158.0](supabase/auth@v2.157.0...v2.158.0) (2024-07-31) ### Features * add hook log entry with `run_hook` action ([supabase#1684](supabase#1684)) ([46491b8](supabase@46491b8)) * MFA (Phone) ([supabase#1668](supabase#1668)) ([ae091aa](supabase@ae091aa)) ### Bug Fixes * maintain backward compatibility for asymmetric JWTs ([supabase#1690](supabase#1690)) ([0ad1402](supabase@0ad1402)) * MFA NewFactor to default to creating unverfied factors ([supabase#1692](supabase#1692)) ([3d448fa](supabase@3d448fa)) * minor spelling errors ([supabase#1688](supabase#1688)) ([6aca52b](supabase@6aca52b)), closes [supabase#1682](supabase#1682) * treat `GOTRUE_MFA_ENABLED` as meaning TOTP enabled on enroll and verify ([supabase#1694](supabase#1694)) ([8015251](supabase@8015251)) * update mfa phone migration to be idempotent ([supabase#1687](supabase#1687)) ([fdff1e7](supabase@fdff1e7)) --- 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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
auth/openapi.yaml
Line 184 in f9df65c
The text was updated successfully, but these errors were encountered: