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 #8972] [MERGED] chore: sync main to next #16583

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/8972
Author: @better-release[bot]
Created: 4/5/2026
Status: ✅ Merged
Merged: 4/5/2026
Merged by: @gustavovalverde

Base: next ← Head: main

📝 Commits (6)

  • b79c045 fix(ci): replace rebase sync with batched merge PR, add auto-retarget (#8957)
  • 4bb24cf fix(ci): exclude promotion PRs from auto-retarget (#8960)
  • 126e92a ci: add auto-changeset generation on PR approval (#8959)
  • 982b505 refactor(ci): drop c-* label prefix, delete pr-analyzer, simplify auto-label (#8963)
  • 7b65767 fix(ci): run tests in merge queue, add summary gate jobs, cover next branch (#8964)
  • 503e95c chore(ci): rename bot identity to better-release (#8970)

📊 Changes

15 files changed (+633 additions, -360 deletions)

View changed files

📝 .cspell/tech-terms.txt (+6 -0)
📝 .github/labeler.yml (+15 -15)
➕ .github/scripts/auto-changeset.ts (+276 -0)
➖ .github/scripts/pr-analyzer.ts (+0 -245)
➕ .github/workflows/auto-changeset.yml (+192 -0)
📝 .github/workflows/auto-label.yml (+0 -19)
➕ .github/workflows/auto-retarget.yml (+75 -0)
📝 .github/workflows/ci.yml (+9 -12)
📝 .github/workflows/e2e.yml (+10 -26)
📝 .github/workflows/promote.yml (+16 -8)
📝 .github/workflows/release.yml (+26 -30)
📝 .github/workflows/verify-changesets.yml (+3 -3)
📝 .github/workflows/zizmor.yml (+1 -1)
📝 .github/zizmor.yml (+3 -0)
📝 knip.jsonc (+1 -1)

📄 Description

Brings stable fixes from main into the next branch.

This PR must be merged by a maintainer using 'Create a merge commit' (not squash, not rebase). This preserves individual fix commits and their verified signatures.

If there are conflicts, resolve them by keeping next's versions for package.json files (next is always ahead of main in version numbers).

Summary by cubic

Syncs stable CI and release automation from main into next. Switches to PR-based main→next sync, adds auto-retargeting, and safe, maintainer-invoked changeset generation.

  • Refactors

    • Replace rebase sync with merge PR in release.yml; preserve signatures and label conflicts.
    • Add auto-retarget.yml to move minor/major PRs from main to next.
    • Add auto-changeset.yml and .github/scripts/auto-changeset.ts for a /changeset command; remove pr-analyzer.ts.
    • Simplify labeler.yml: drop c-* prefixes and remove the refinement step.
    • CI/E2E: run on next, enable tests in merge queue, and add “alls-green” aggregator jobs.
    • Rename bot to better-release[bot]; expand security checks to next; update knip to ignore tsx.

  • Migration

    • Merge using Create a merge commit (not squash or rebase).
    • If conflicts occur, keep next’s versions for package.json files.

Written for commit 503e95c7fd. 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/8972 **Author:** [@better-release[bot]](https://github.com/apps/better-release) **Created:** 4/5/2026 **Status:** ✅ Merged **Merged:** 4/5/2026 **Merged by:** [@gustavovalverde](https://github.com/gustavovalverde) **Base:** `next` ← **Head:** `main` --- ### 📝 Commits (6) - [`b79c045`](https://github.com/better-auth/better-auth/commit/b79c0459275f2cb25d26c151cb09c2e3af4e8fa8) fix(ci): replace rebase sync with batched merge PR, add auto-retarget (#8957) - [`4bb24cf`](https://github.com/better-auth/better-auth/commit/4bb24cfd75ae22816ab0459dfc7d062aa2c6ac40) fix(ci): exclude promotion PRs from auto-retarget (#8960) - [`126e92a`](https://github.com/better-auth/better-auth/commit/126e92ab243aba059aeda666f25bbd345b857968) ci: add auto-changeset generation on PR approval (#8959) - [`982b505`](https://github.com/better-auth/better-auth/commit/982b5050996c4f2ea67c477d26019947637ed059) refactor(ci): drop `c-*` label prefix, delete pr-analyzer, simplify auto-label (#8963) - [`7b65767`](https://github.com/better-auth/better-auth/commit/7b6576762882f7a5e6361b63ea794556e487d197) fix(ci): run tests in merge queue, add summary gate jobs, cover next branch (#8964) - [`503e95c`](https://github.com/better-auth/better-auth/commit/503e95c7fd423b636419ce467067ddaaee8f4c85) chore(ci): rename bot identity to better-release (#8970) ### 📊 Changes **15 files changed** (+633 additions, -360 deletions) <details> <summary>View changed files</summary> 📝 `.cspell/tech-terms.txt` (+6 -0) 📝 `.github/labeler.yml` (+15 -15) ➕ `.github/scripts/auto-changeset.ts` (+276 -0) ➖ `.github/scripts/pr-analyzer.ts` (+0 -245) ➕ `.github/workflows/auto-changeset.yml` (+192 -0) 📝 `.github/workflows/auto-label.yml` (+0 -19) ➕ `.github/workflows/auto-retarget.yml` (+75 -0) 📝 `.github/workflows/ci.yml` (+9 -12) 📝 `.github/workflows/e2e.yml` (+10 -26) 📝 `.github/workflows/promote.yml` (+16 -8) 📝 `.github/workflows/release.yml` (+26 -30) 📝 `.github/workflows/verify-changesets.yml` (+3 -3) 📝 `.github/workflows/zizmor.yml` (+1 -1) 📝 `.github/zizmor.yml` (+3 -0) 📝 `knip.jsonc` (+1 -1) </details> ### 📄 Description Brings stable fixes from main into the next branch. **This PR must be merged by a maintainer using 'Create a merge commit'** (not squash, not rebase). This preserves individual fix commits and their verified signatures. If there are conflicts, resolve them by keeping next's versions for `package.json` files (next is always ahead of main in version numbers). <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Syncs stable CI and release automation from main into next. Switches to PR-based main→next sync, adds auto-retargeting, and safe, maintainer-invoked changeset generation. - **Refactors** - Replace rebase sync with merge PR in `release.yml`; preserve signatures and label conflicts. - Add `auto-retarget.yml` to move minor/major PRs from `main` to `next`. - Add `auto-changeset.yml` and `.github/scripts/auto-changeset.ts` for a `/changeset` command; remove `pr-analyzer.ts`. - Simplify `labeler.yml`: drop `c-*` prefixes and remove the refinement step. - CI/E2E: run on `next`, enable tests in merge queue, and add “alls-green” aggregator jobs. - Rename bot to `better-release[bot]`; expand security checks to `next`; update `knip` to ignore `tsx`. - **Migration** - Merge using Create a merge commit (not squash or rebase). - If conflicts occur, keep `next`’s versions for `package.json` files. <sup>Written for commit 503e95c7fd423b636419ce467067ddaaee8f4c85. 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:35:33 -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#16583
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?