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 #8944] [MERGED] chore: add all packages to changesets fixed group #16562

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

📋 Pull Request Information

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

Base: main ← Head: chore/changeset-fixed-group

📝 Commits (1)

  • 54aa1c5 chore: add all packages to changesets fixed group

📊 Changes

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

View changed files

📝 .changeset/config.json (+24 -1)

📄 Description

Summary

Add all 20 published packages to the changesets fixed group so they always share the same version number.

Previously only better-auth and @better-auth/core were locked together. This caused version drift where some packages would be at 1.6.0-beta.0 and others at 1.5.7-beta.0 in the same release.

Summary by cubic

Add all 20 published packages to the changesets fixed group so they always share the same version number. This prevents version drift and ensures releasing any package bumps the version for all.

Written for commit 54aa1c58cb. 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/8944 **Author:** [@gustavovalverde](https://github.com/gustavovalverde) **Created:** 4/3/2026 **Status:** ✅ Merged **Merged:** 4/3/2026 **Merged by:** [@gustavovalverde](https://github.com/gustavovalverde) **Base:** `main` ← **Head:** `chore/changeset-fixed-group` --- ### 📝 Commits (1) - [`54aa1c5`](https://github.com/better-auth/better-auth/commit/54aa1c58cb2be04be7ed6675d64779bc9c7ad2f0) chore: add all packages to changesets fixed group ### 📊 Changes **1 file changed** (+24 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.changeset/config.json` (+24 -1) </details> ### 📄 Description ## Summary Add all 20 published packages to the changesets `fixed` group so they always share the same version number. Previously only `better-auth` and `@better-auth/core` were locked together. This caused version drift where some packages would be at `1.6.0-beta.0` and others at `1.5.7-beta.0` in the same release. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Add all 20 published packages to the `changesets` `fixed` group so they always share the same version number. This prevents version drift and ensures releasing any package bumps the version for all. <sup>Written for commit 54aa1c58cb2be04be7ed6675d64779bc9c7ad2f0. 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:34:44 -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#16562
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?