github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-24 16:11:53 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #4772] v1.3.13 failed to release #10058

New Issue
Closed
opened 2026-04-13 05:58:09 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-13 05:58:09 -05:00
Owner
Copy Link

Originally created by @kevinmarrec on GitHub (Sep 19, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/4772

To Reproduce

https://github.com/better-auth/better-auth/actions/runs/17848983106

Sounds like the commit it not present on main, somehow.

@himself65

Current vs. Expected behavior

Expected last npm tag to be v1.3.13

Which area(s) are affected? (Select all that apply)

Package

Additional Context

Probably related to https://github.com/better-auth/better-auth/issues/4757 (v1.3.x Maintenance Plan)

Suggestions

Update Release workflow to work with v1.3.x-latest branch.

Originally created by @kevinmarrec on GitHub (Sep 19, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/4772 ### To Reproduce https://github.com/better-auth/better-auth/actions/runs/17848983106 Sounds like the commit it not present on `main`, somehow. @himself65 ### Current vs. Expected behavior Expected last npm tag to be **v1.3.13** ### Which area(s) are affected? (Select all that apply) Package ### Additional Context Probably related to https://github.com/better-auth/better-auth/issues/4757 (v1.3.x Maintenance Plan) ### Suggestions Update **Release** workflow to work with `v1.3.x-latest` branch.
GiteaMirror added the lockedbug labels 2026-04-13 05:58:09 -05:00
GiteaMirror commented 2026-04-13 05:58:11 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Sep 19, 2025):

Oh

<!-- gh-comment-id:3313390407 --> @himself65 commented on GitHub (Sep 19, 2025): Oh
GiteaMirror commented 2026-04-13 05:58:11 -05:00
Author
Owner
Copy Link

@himself65 commented on GitHub (Sep 19, 2025):

Fixed, I added a CI fix

a3e46c1b70
https://www.npmjs.com/package/better-auth/v/1.3.13

<!-- gh-comment-id:3313422288 --> @himself65 commented on GitHub (Sep 19, 2025): Fixed, I added a CI fix https://github.com/better-auth/better-auth/commit/a3e46c1b70f008cdca751144741e7b5724bfc4e1 https://www.npmjs.com/package/better-auth/v/1.3.13
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 bug locked
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#10058
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?