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

[PR #8993] [MERGED] chore: remove pending pr-8927 changeset #16602

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/8993
Author: @gustavovalverde
Created: 4/6/2026
Status: ✅ Merged
Merged: 4/6/2026
Merged by: @gustavovalverde

Base: next ← Head: codex/remove-pr-8927-changeset

📝 Commits (1)

  • 4c4aa89 chore(release): remove pending pr-8927 changeset from next

📊 Changes

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

View changed files

➖ .changeset/pr-8927.md (+0 -5)

📄 Description

Summary

  • remove .changeset/pr-8927.md from next
  • keep the #8927 code changes already synced from main
  • preserve the current 1.6.0 promotion path without introducing an extra patch bump

Why

After main was synced back into next, the code from #8927 and its patch changeset were both present on next. The code is fine to keep, but the changeset would cause a fresh promote/version run to schedule another patch release.

This PR removes only the pending changeset so the existing 1.6.0 promotion PR can stay on the exact intended version.

Validation

  • confirmed the diff is only the deletion of .changeset/pr-8927.md
  • confirmed package versions on next remain at 1.6.0

Summary by cubic

Removes .changeset/pr-8927.md from next to prevent an unnecessary patch release. Keeps the #8927 code and preserves the existing 1.6.0 promotion.

Written for commit 4c4aa89d9a. Summary will update 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/8993 **Author:** [@gustavovalverde](https://github.com/gustavovalverde) **Created:** 4/6/2026 **Status:** ✅ Merged **Merged:** 4/6/2026 **Merged by:** [@gustavovalverde](https://github.com/gustavovalverde) **Base:** `next` ← **Head:** `codex/remove-pr-8927-changeset` --- ### 📝 Commits (1) - [`4c4aa89`](https://github.com/better-auth/better-auth/commit/4c4aa89d9a519a00b6ac63fc255e4a585e7b576d) chore(release): remove pending pr-8927 changeset from next ### 📊 Changes **1 file changed** (+0 additions, -5 deletions) <details> <summary>View changed files</summary> ➖ `.changeset/pr-8927.md` (+0 -5) </details> ### 📄 Description ## Summary - remove `.changeset/pr-8927.md` from `next` - keep the `#8927` code changes already synced from `main` - preserve the current `1.6.0` promotion path without introducing an extra patch bump ## Why After `main` was synced back into `next`, the code from `#8927` and its patch changeset were both present on `next`. The code is fine to keep, but the changeset would cause a fresh promote/version run to schedule another patch release. This PR removes only the pending changeset so the existing `1.6.0` promotion PR can stay on the exact intended version. ## Validation - confirmed the diff is only the deletion of `.changeset/pr-8927.md` - confirmed package versions on `next` remain at `1.6.0` <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Removes `.changeset/pr-8927.md` from `next` to prevent an unnecessary patch release. Keeps the #8927 code and preserves the existing `1.6.0` promotion. <sup>Written for commit 4c4aa89d9a519a00b6ac63fc255e4a585e7b576d. Summary will update 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-04-13 10:36:14 -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#16602
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?