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 #8979] [MERGED] fix(ci): skip changeset verification on sync PRs (main → next) #25243

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

📋 Pull Request Information

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

Base: main ← Head: fix/verify-changesets-sync

📝 Commits (1)

  • 812f93d fix(ci): skip changeset verification on sync PRs (main → next)

📊 Changes

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

View changed files

📝 .github/workflows/verify-changesets.yml (+1 -0)

📄 Description

Summary

  • The sync PR (main → next) carries package changes but no changeset — this is correct since it's a structural sync, not a feature.
  • verify-changesets.yml already excluded promote PRs (next → main) but not the reverse direction.
  • The workflow was triggered by cubic-dev-ai[bot] (label sync), bypassing the actor-based exclusion for better-release[bot].
  • Fix: add structural exclusion for head=main && base=next (same pattern as the promote PR exclusion).

Context

Sync PR #8976 failed: https://github.com/better-auth/better-auth/actions/runs/24012825893/job/70027096985

Summary by cubic

Skip changeset verification for structural sync PRs from main to next. This mirrors the existing next → main exclusion and prevents false failures on bot-triggered syncs (e.g., cubic-dev-ai[bot], github-actions[bot], better-release[bot]).

Written for commit 812f93d900. 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/8979 **Author:** [@gustavovalverde](https://github.com/gustavovalverde) **Created:** 4/6/2026 **Status:** ✅ Merged **Merged:** 4/6/2026 **Merged by:** [@gustavovalverde](https://github.com/gustavovalverde) **Base:** `main` ← **Head:** `fix/verify-changesets-sync` --- ### 📝 Commits (1) - [`812f93d`](https://github.com/better-auth/better-auth/commit/812f93d900a15bf8d2f0c5e22881fa384d3ca742) fix(ci): skip changeset verification on sync PRs (main → next) ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/verify-changesets.yml` (+1 -0) </details> ### 📄 Description ## Summary - The sync PR (`main → next`) carries package changes but no changeset — this is correct since it's a structural sync, not a feature. - `verify-changesets.yml` already excluded promote PRs (`next → main`) but not the reverse direction. - The workflow was triggered by `cubic-dev-ai[bot]` (label sync), bypassing the actor-based exclusion for `better-release[bot]`. - Fix: add structural exclusion for `head=main && base=next` (same pattern as the promote PR exclusion). ## Context Sync PR #8976 failed: https://github.com/better-auth/better-auth/actions/runs/24012825893/job/70027096985 <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Skip changeset verification for structural sync PRs from `main` to `next`. This mirrors the existing `next → main` exclusion and prevents false failures on bot-triggered syncs (e.g., `cubic-dev-ai[bot]`, `github-actions[bot]`, `better-release[bot]`). <sup>Written for commit 812f93d900a15bf8d2f0c5e22881fa384d3ca742. 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:47:07 -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#25243
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?