Repository navigation
feat(oauth): hardcoded client ID, instead of DCR - #179
Merged
Merged
Conversation
andrinoff
force-pushed
the
feat/verified-oauth
branch
from
August 18, 2026 10:33
5be4443 to
aacb828
Compare
Signed-off-by: drew <me@andrinoff.com>
andrinoff
force-pushed
the
feat/verified-oauth
branch
from
August 18, 2026 21:03
aacb828 to
53bfc6a
Compare
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
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.
What?
Removes DCR (dynamic client registration) and adds a hardcoded client ID
Why?
For consistency and also to show a verified badge on the OAuth screen.
NOTE: not ready to merge, this PR uses Resend CLI's client ID, not ours