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 #9200] [MERGED] chore(cimd): add to fixed version group and align at 1.7.0-beta.1 #25398

New Issue
Closed
opened 2026-04-15 22:52:10 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 22:52:10 -05:00
Owner
Copy Link

📋 Pull Request Information

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

Base: next ← Head: chore/align-cimd-version

📝 Commits (1)

  • 364184a chore(cimd): add to fixed version group and align at 1.7.0-beta.1

📊 Changes

2 files changed (+2 additions, -1 deletions)

View changed files

📝 .changeset/config.json (+1 -0)
📝 packages/cimd/package.json (+1 -1)

📄 Description

The v1.7.0-beta.1 release failed to publish @better-auth/cimd because the package was created on next (#9159) without being added to the fixed group in .changeset/config.json. Every other package bumped from beta.0 to beta.1 as a group; CIMD stayed at beta.0 and hit a second issue: it had never been published to npm before, so OIDC trusted publishing could not bootstrap the package name.

@better-auth/cimd@1.7.0-beta.0 was published manually to create the npm entry, and a trusted publisher config has been set for the package. This PR:

  • Adds @better-auth/cimd to the fixed version group so future releases keep it in lockstep with the rest of the workspace.
  • Bumps packages/cimd/package.json to 1.7.0-beta.1 so changeset publish detects the out-of-sync state and publishes CIMD@1.7.0-beta.1 via OIDC on merge.

On merge, the changesets publish step will also trigger the release-notes generation and GitHub Release creation that were skipped when the original v1.7.0-beta.1 run failed on CIMD. The release-notes script diffs the current .changeset/pre.json against v1.7.0-beta.0's pre.json, so the recovered notes will cover all 12 changesets consumed in the beta.1 cycle (not just CIMD).

Summary by cubic

Adds @better-auth/cimd to the fixed version group and bumps it to 1.7.0-beta.1. Fixes the beta.1 publish gap and keeps CIMD in lockstep with the workspace.

  • Bug Fixes
    • Add @better-auth/cimd to .changeset/config.json fixed group to align versions with other packages.
    • Set packages/cimd/package.json to 1.7.0-beta.1 so changeset publish releases via OIDC and generates the beta.1 release notes.

Written for commit 364184a1b7. 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/9200 **Author:** [@gustavovalverde](https://github.com/gustavovalverde) **Created:** 4/15/2026 **Status:** ✅ Merged **Merged:** 4/15/2026 **Merged by:** [@gustavovalverde](https://github.com/gustavovalverde) **Base:** `next` ← **Head:** `chore/align-cimd-version` --- ### 📝 Commits (1) - [`364184a`](https://github.com/better-auth/better-auth/commit/364184a1b7e1af41ca34095ea428ea655c616775) chore(cimd): add to fixed version group and align at 1.7.0-beta.1 ### 📊 Changes **2 files changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.changeset/config.json` (+1 -0) 📝 `packages/cimd/package.json` (+1 -1) </details> ### 📄 Description The v1.7.0-beta.1 release failed to publish `@better-auth/cimd` because the package was created on `next` (#9159) without being added to the `fixed` group in `.changeset/config.json`. Every other package bumped from `beta.0` to `beta.1` as a group; CIMD stayed at `beta.0` and hit a second issue: it had never been published to npm before, so OIDC trusted publishing could not bootstrap the package name. `@better-auth/cimd@1.7.0-beta.0` was published manually to create the npm entry, and a trusted publisher config has been set for the package. This PR: - Adds `@better-auth/cimd` to the fixed version group so future releases keep it in lockstep with the rest of the workspace. - Bumps `packages/cimd/package.json` to `1.7.0-beta.1` so `changeset publish` detects the out-of-sync state and publishes `CIMD@1.7.0-beta.1` via OIDC on merge. On merge, the changesets publish step will also trigger the release-notes generation and GitHub Release creation that were skipped when the original v1.7.0-beta.1 run failed on CIMD. The release-notes script diffs the current `.changeset/pre.json` against `v1.7.0-beta.0`'s pre.json, so the recovered notes will cover all 12 changesets consumed in the beta.1 cycle (not just CIMD). <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Adds `@better-auth/cimd` to the fixed version group and bumps it to `1.7.0-beta.1`. Fixes the beta.1 publish gap and keeps CIMD in lockstep with the workspace. - **Bug Fixes** - Add `@better-auth/cimd` to `.changeset/config.json` fixed group to align versions with other packages. - Set `packages/cimd/package.json` to `1.7.0-beta.1` so `changeset publish` releases via OIDC and generates the beta.1 release notes. <sup>Written for commit 364184a1b7e1af41ca34095ea428ea655c616775. 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-15 22:52:10 -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#25398
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?