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 #6475] [MERGED] ci: remove NODE_AUTH_TOKEN during publish #6692

New Issue
Closed
opened 2026-03-13 13:08:23 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 13:08:23 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6475
Author: @himself65
Created: 12/2/2025
Status: ✅ Merged
Merged: 12/2/2025
Merged by: @himself65

Base: canary ← Head: himself65/2025/12/02/remove-token

📝 Commits (1)

  • 1534895 ci: remove NODE_AUTH_TOKEN during publish

📊 Changes

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

View changed files

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

📄 Description

Summary by cubic

Remove NODE_AUTH_TOKEN from the npm publish step to avoid passing the token via env. Publishing now uses the existing npm auth configuration (e.g., setup-node/.npmrc) with provenance still enabled.

Written for commit 15348959e7. Summary will update automatically 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/6475 **Author:** [@himself65](https://github.com/himself65) **Created:** 12/2/2025 **Status:** ✅ Merged **Merged:** 12/2/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `himself65/2025/12/02/remove-token` --- ### 📝 Commits (1) - [`1534895`](https://github.com/better-auth/better-auth/commit/15348959e78af8ad874e7713569de29a6c17757a) ci: remove `NODE_AUTH_TOKEN` during publish ### 📊 Changes **1 file changed** (+0 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+0 -1) </details> ### 📄 Description <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Remove NODE_AUTH_TOKEN from the npm publish step to avoid passing the token via env. Publishing now uses the existing npm auth configuration (e.g., setup-node/.npmrc) with provenance still enabled. <sup>Written for commit 15348959e78af8ad874e7713569de29a6c17757a. Summary will update automatically 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-03-13 13:08:23 -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#6692
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?