github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-06-02 20:36:19 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #2251] [MERGED] Fix for #2250 : Checking if User is intended recipient of Invite is casesensetive #12475

New Issue
Closed
opened 2026-04-13 08:24:24 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 08:24:24 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/2251
Author: @SNRSE
Created: 4/13/2025
Status: ✅ Merged
Merged: 4/13/2025
Merged by: @Bekacru

Base: main ← Head: main

📝 Commits (2)

  • 6954e45 convert Email to Lowercase to check in Invite
  • 20c3275 Update crud-invites.ts

📊 Changes

1 file changed (+4 additions, -4 deletions)

View changed files

📝 packages/better-auth/src/plugins/organization/routes/crud-invites.ts (+4 -4)

📄 Description

This resolves a bug where, while you can use
Email@example.com to log into the account email@example.com. Inviting Email@example.com would mean they can not accept the invite.

This is done by using .tolowercase on both emails before comparing them

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/2251 **Author:** [@SNRSE](https://github.com/SNRSE) **Created:** 4/13/2025 **Status:** ✅ Merged **Merged:** 4/13/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`6954e45`](https://github.com/better-auth/better-auth/commit/6954e45c511301aa683755293b79d40077fcfdfb) convert Email to Lowercase to check in Invite - [`20c3275`](https://github.com/better-auth/better-auth/commit/20c327557da62859faccb2221f00a4b62f045da0) Update crud-invites.ts ### 📊 Changes **1 file changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/plugins/organization/routes/crud-invites.ts` (+4 -4) </details> ### 📄 Description This resolves a bug where, while you can use Email@example.com to log into the account email@example.com. Inviting Email@example.com would mean they can not accept the invite. This is done by using .tolowercase on both emails before comparing them --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 08:24:24 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#12475
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?