github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #4391] [MERGED] docs: jwt usage with bearer plugin wording #5354

New Issue
Closed
opened 2026-03-13 12:20:00 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 12:20:00 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4391
Author: @ibbycs
Created: 9/3/2025
Status: ✅ Merged
Merged: 9/3/2025
Merged by: @himself65

Base: canary ← Head: docs/jwt-usage-with-bearer-plugin

📝 Commits (1)

  • 6ada14e docs: jwt usage wording with bearer plugin

📊 Changes

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

View changed files

📝 docs/content/docs/plugins/jwt.mdx (+1 -1)

📄 Description

Update wording to make it clear that this is only neccessary if the bearer plugin has been added to configuration

Summary by cubic

Clarified JWT docs: the Authorization header with the token is only required if the bearer plugin is enabled in the auth configuration.

🔄 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/4391 **Author:** [@ibbycs](https://github.com/ibbycs) **Created:** 9/3/2025 **Status:** ✅ Merged **Merged:** 9/3/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/jwt-usage-with-bearer-plugin` --- ### 📝 Commits (1) - [`6ada14e`](https://github.com/better-auth/better-auth/commit/6ada14ed1a3fb62ef0cb9bdd35d2d04f0067984a) docs: jwt usage wording with bearer plugin ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/plugins/jwt.mdx` (+1 -1) </details> ### 📄 Description Update wording to make it clear that this is only neccessary if the `bearer` plugin has been added to configuration <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Clarified JWT docs: the Authorization header with the token is only required if the bearer plugin is enabled in the auth configuration. <!-- End of auto-generated description by cubic. --> --- <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-03-13 12:20:00 -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#5354
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?