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

[GH-ISSUE #6328] Provenance attestation downgrade #27807

New Issue
Closed
opened 2026-04-17 19:01:57 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-17 19:01:57 -05:00
Owner
Copy Link

Originally created by @Jerboas86 on GitHub (Nov 26, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6328

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

Earlier versions had provenance attestation, but the last version is missing it.
The package will be flag as high risk by package manager like pnpm if dependencies update is made under trustPolicy: "no-downgrade".
Rightly so, since this may mean that the package has been compromised by a supply chain attack.

Current vs. Expected behavior

The provenance attestation that has been added in 1.4.2 beta versions should be also present in v1.4.2

What version of Better Auth are you using?

1.4.2

System info

N/A

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

Package

Auth config (if applicable)

n/a

Additional context

No response

Originally created by @Jerboas86 on GitHub (Nov 26, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6328 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce Earlier versions had provenance attestation, but the last version is missing it. The package will be flag as high risk by package manager like pnpm if dependencies update is made under trustPolicy: "no-downgrade". Rightly so, since this may mean that the package has been compromised by a supply chain attack. ### Current vs. Expected behavior The provenance attestation that has been added in 1.4.2 beta versions should be also present in v1.4.2 ### What version of Better Auth are you using? 1.4.2 ### System info ```bash N/A ``` ### Which area(s) are affected? (Select all that apply) Package ### Auth config (if applicable) ```typescript n/a ``` ### Additional context _No response_
GiteaMirror added the locked label 2026-04-17 19:01:57 -05:00
GiteaMirror commented 2026-04-17 19:01:59 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Nov 26, 2025):

(Waiting for a message tagged with @better-auth-agent to proceed.)

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3580076478 --> @better-auth-agent[bot] commented on GitHub (Nov 26, 2025): (Waiting for a message tagged with @better-auth-agent to proceed.) <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)
GiteaMirror commented 2026-04-17 19:02:00 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Nov 26, 2025):

Hi @Jerboas86! I'm Dosu and I’m helping the better-auth team.

Provenance attestation was present in 1.4.2-beta.4 but missing in the final 1.4.2 release due to the release workflow not including the necessary provenance steps. This was a known issue and has now been fixed—PR #6272 adds the --provenance flag to all publish commands and updates the release workflow to enable provenance attestation for future releases, addressing supply chain security concerns and package manager trust policies like pnpm's trustPolicy: "no-downgrade" source.

If you need provenance attestation, hold off on upgrading to 1.4.2 until the next release is published with the fix. The team is also migrating to npm trusted publishing for even stronger guarantees source.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

<!-- gh-comment-id:3580104624 --> @dosubot[bot] commented on GitHub (Nov 26, 2025): <!-- Greeting --> Hi @Jerboas86! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team. <!-- Answer --> Provenance attestation was present in 1.4.2-beta.4 but missing in the final 1.4.2 release due to the release workflow not including the necessary provenance steps. This was a known issue and has now been fixed—PR #6272 adds the `--provenance` flag to all publish commands and updates the release workflow to enable provenance attestation for future releases, addressing supply chain security concerns and package manager trust policies like pnpm's `trustPolicy: "no-downgrade"` [source](https://github.com/better-auth/better-auth/pull/6272). If you need provenance attestation, hold off on upgrading to 1.4.2 until the next release is published with the fix. The team is also migrating to npm trusted publishing for even stronger guarantees [source](https://github.com/better-auth/better-auth/issues/6261). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bf03973d-7847-49aa-b34e-250c31c4c901?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Provenance%20attestation%20was%20present%20in%201.4.2-beta.4%20but%20missing%20in%20the%20final%201.4.2%20release%20due%20to%20the%20release%20workflow%20not%20including%20the%20necessary%20provenance%20steps.%20This%20was%20a%20known%20issue%20and%20has%20now%20been%20fixed%E2%80%94PR%20%236272%20adds%20the%20%60--provenance%60%20flag%20to%20all%20publish%20commands%20and%20updates%20the%20release%20workflow%20to%20enable%20provenance%20attestation%20for%20future%20releases%2C%20addressing%20supply%20chain%20security%20concerns%20and%20package%20manager%20trust%20policies%20like%20pnpm%27s%20%60trustPolicy%3A%20%22no-downgrade%22%60%20%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/pull/6272%29.%0A%0AIf%20you%20need%20provenance%20attestation%2C%20hold%20off%20on%20upgrading%20to%201.4.2%20until%20the%20next%20release%20is%20published%20with%20the%20fix.%20The%20team%20is%20also%20migrating%20to%20npm%20trusted%20publishing%20for%20even%20stronger%20guarantees%20%5Bsource%5D%28https%3A//github.com/better-auth/better-auth/issues/6261%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/6328)
GiteaMirror commented 2026-04-17 19:02:01 -05:00
Author
Owner
Copy Link

@Jerboas86 commented on GitHub (Nov 26, 2025):

@dosu The provenance attestation is still missing in v1.4.3. Only the beta releases seems to have their provenance attested.

<!-- gh-comment-id:3583151747 --> @Jerboas86 commented on GitHub (Nov 26, 2025): @dosu The provenance attestation is still missing in v1.4.3. Only the beta releases seems to have their provenance attested.
GiteaMirror commented 2026-04-17 19:02:01 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Nov 26, 2025):

Provenance attestation is missing in v1.4.3 stable because the release workflow at that time didn't include the necessary --provenance flag or the required id-token: write permission. Beta releases like 1.4.2-beta.4 had provenance because the flag was manually included, but stable releases did not due to workflow configuration. This issue was fixed in PR #6272, which updates the release workflow and publish scripts to enable provenance attestation for all future releases.

There’s no workaround for v1.4.3—if you need provenance attestation, you’ll need to wait for the next stable release after this fix. The team is also migrating to npm trusted publishing, which will provide automatic provenance attestation and stronger supply chain security (details).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

<!-- gh-comment-id:3583158461 --> @dosubot[bot] commented on GitHub (Nov 26, 2025): <!-- Answer --> Provenance attestation is missing in v1.4.3 stable because the release workflow at that time didn't include the necessary `--provenance` flag or the required `id-token: write` permission. Beta releases like 1.4.2-beta.4 had provenance because the flag was manually included, but stable releases did not due to workflow configuration. This issue was fixed in [PR #6272](https://github.com/better-auth/better-auth/pull/6272), which updates the release workflow and publish scripts to enable provenance attestation for all future releases. There’s no workaround for v1.4.3—if you need provenance attestation, you’ll need to wait for the next stable release after this fix. The team is also migrating to npm trusted publishing, which will provide automatic provenance attestation and stronger supply chain security ([details](https://github.com/better-auth/better-auth/issues/6261)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/30eb6c1f-c907-4efa-a64a-ed096bed2a05?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Provenance%20attestation%20is%20missing%20in%20v1.4.3%20stable%20because%20the%20release%20workflow%20at%20that%20time%20didn%27t%20include%20the%20necessary%20%60--provenance%60%20flag%20or%20the%20required%20%60id-token%3A%20write%60%20permission.%20Beta%20releases%20like%201.4.2-beta.4%20had%20provenance%20because%20the%20flag%20was%20manually%20included%2C%20but%20stable%20releases%20did%20not%20due%20to%20workflow%20configuration.%20This%20issue%20was%20fixed%20in%20%5BPR%20%236272%5D%28https%3A//github.com/better-auth/better-auth/pull/6272%29%2C%20which%20updates%20the%20release%20workflow%20and%20publish%20scripts%20to%20enable%20provenance%20attestation%20for%20all%20future%20releases.%0A%0AThere%E2%80%99s%20no%20workaround%20for%20v1.4.3%E2%80%94if%20you%20need%20provenance%20attestation%2C%20you%E2%80%99ll%20need%20to%20wait%20for%20the%20next%20stable%20release%20after%20this%20fix.%20The%20team%20is%20also%20migrating%20to%20npm%20trusted%20publishing%2C%20which%20will%20provide%20automatic%20provenance%20attestation%20and%20stronger%20supply%20chain%20security%20%28%5Bdetails%5D%28https%3A//github.com/better-auth/better-auth/issues/6261%29%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/6328)
GiteaMirror commented 2026-04-17 19:02:02 -05:00
Author
Owner
Copy Link

@Jerboas86 commented on GitHub (Dec 3, 2025):

Fixed in v1.4.5

<!-- gh-comment-id:3605622214 --> @Jerboas86 commented on GitHub (Dec 3, 2025): Fixed in v1.4.5
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 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#27807
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?