github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 15:42:09 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #4088] [MERGED] chore: bump better-call #13427

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4088
Author: @himself65
Created: 8/19/2025
Status: ✅ Merged
Merged: 8/19/2025
Merged by: @himself65

Base: canary ← Head: himself65/2025/08/19/bump

📝 Commits (1)

📊 Changes

2 files changed (+16 additions, -14 deletions)

View changed files

📝 pnpm-lock.yaml (+15 -13)
📝 pnpm-workspace.yaml (+1 -1)

📄 Description

Related: https://github.com/better-auth/better-auth/issues/4082

Remove the caret in case of same thing happens

Summary by cubic

Bumped better-call to 1.0.15 across the workspace to pick up the latest fixes and keep versions consistent. Updated the workspace catalog and lockfile accordingly.

  • Dependencies
    • Set catalog "better-call" to 1.0.15 and updated all importers.
    • Regenerated pnpm lock for better-call@1.0.15 integrity/snapshots.
    • Minor lockfile adjustments for @types/node and undici-types (deduped/optional).

🔄 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/4088 **Author:** [@himself65](https://github.com/himself65) **Created:** 8/19/2025 **Status:** ✅ Merged **Merged:** 8/19/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `himself65/2025/08/19/bump` --- ### 📝 Commits (1) - [`3282260`](https://github.com/better-auth/better-auth/commit/3282260bad84dc2b62f582f9aec5a220e1b19887) chore: bump `better-call` ### 📊 Changes **2 files changed** (+16 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `pnpm-lock.yaml` (+15 -13) 📝 `pnpm-workspace.yaml` (+1 -1) </details> ### 📄 Description Related: https://github.com/better-auth/better-auth/issues/4082 Remove the caret in case of same thing happens <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Bumped better-call to 1.0.15 across the workspace to pick up the latest fixes and keep versions consistent. Updated the workspace catalog and lockfile accordingly. - **Dependencies** - Set catalog "better-call" to 1.0.15 and updated all importers. - Regenerated pnpm lock for better-call@1.0.15 integrity/snapshots. - Minor lockfile adjustments for @types/node and undici-types (deduped/optional). <!-- 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-04-13 08:55:56 -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#13427
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?