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 #6546] docs: add paragraph specifying need for cookie passage for server methods #6735

New Issue
Open
opened 2026-03-13 13:09:50 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 13:09:50 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6546
Author: @DougInAMug
Created: 12/5/2025
Status: 🔄 Open

Base: canary ← Head: docs_mention-cookies-for-server-methods

📝 Commits (2)

  • 2dbdef8 add paragraph specifying need for cookie passage for server methods
  • eac8405 fix links to start with

📊 Changes

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

View changed files

📝 docs/content/docs/authentication/email-password.mdx (+2 -0)

📄 Description

Further to Discord thread with Max, this documentation change refers readers to necessary requirements for server signIn/signUp methods.

Summary by cubic

Added a note in the Email/Password auth docs that server methods (e.g., signUpEmail) require passing cookies back to the client. Included links to Next and SvelteKit integrations for server-action cookies to guide configuration.

Written for commit eac840519fecdd5c89506ab00549280ca7e2979e. Summary will update automatically on new commits.

🔄 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/6546 **Author:** [@DougInAMug](https://github.com/DougInAMug) **Created:** 12/5/2025 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `docs_mention-cookies-for-server-methods` --- ### 📝 Commits (2) - [`2dbdef8`](https://github.com/better-auth/better-auth/commit/2dbdef85e63dac8cc2e0952f4d81d8298bfa3a52) add paragraph specifying need for cookie passage for server methods - [`eac8405`](https://github.com/better-auth/better-auth/commit/eac840519fecdd5c89506ab00549280ca7e2979e) fix links to start with ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/authentication/email-password.mdx` (+2 -0) </details> ### 📄 Description Further to [Discord thread](https://discord.com/channels/1288403910284935179/1446159987813388299/1446159987813388299) with Max, this documentation change refers readers to necessary requirements for server signIn/signUp methods. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added a note in the Email/Password auth docs that server methods (e.g., signUpEmail) require passing cookies back to the client. Included links to Next and SvelteKit integrations for server-action cookies to guide configuration. <sup>Written for commit eac840519fecdd5c89506ab00549280ca7e2979e. Summary will update automatically on new commits.</sup> <!-- 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 13:09:50 -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#6735
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?