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 #4137] [MERGED] chore: fix turborepo cache hit issue #22113

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4137
Author: @himself65
Created: 8/21/2025
Status: ✅ Merged
Merged: 8/21/2025
Merged by: @himself65

Base: canary ← Head: himself65/2025/08/21/cache

📝 Commits (3)

  • 6dedfad chore: fix turborepo cache hit issue
  • d72d253 fix: move env into deeper turbo.json
  • af2d1cc fix: move env into deeper turbo.json

📊 Changes

3 files changed (+37 additions, -19 deletions)

View changed files

➕ demo/nextjs/turbo.json (+26 -0)
➕ docs/turbo.json (+9 -0)
📝 turbo.json (+2 -19)

📄 Description

Summary by cubic

Fix Turborepo build cache accuracy by tracking .env changes and tightening Next.js outputs. This prevents stale builds and avoids caching .next/cache.

  • Bug Fixes
    • Added build inputs: TURBO_DEFAULT, .env*
    • Updated outputs: .next/, !.next/cache/, dist/**

🔄 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/4137 **Author:** [@himself65](https://github.com/himself65) **Created:** 8/21/2025 **Status:** ✅ Merged **Merged:** 8/21/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `himself65/2025/08/21/cache` --- ### 📝 Commits (3) - [`6dedfad`](https://github.com/better-auth/better-auth/commit/6dedfadead74e63421194ce7a201088cd1ae9a18) chore: fix turborepo cache hit issue - [`d72d253`](https://github.com/better-auth/better-auth/commit/d72d253f8442adb7bed2e0fc0a858e75cef726a0) fix: move env into deeper turbo.json - [`af2d1cc`](https://github.com/better-auth/better-auth/commit/af2d1cc341d190418f6d6737b6e904603cd9200a) fix: move env into deeper turbo.json ### 📊 Changes **3 files changed** (+37 additions, -19 deletions) <details> <summary>View changed files</summary> ➕ `demo/nextjs/turbo.json` (+26 -0) ➕ `docs/turbo.json` (+9 -0) 📝 `turbo.json` (+2 -19) </details> ### 📄 Description <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Fix Turborepo build cache accuracy by tracking .env changes and tightening Next.js outputs. This prevents stale builds and avoids caching .next/cache. - **Bug Fixes** - Added build inputs: $TURBO_DEFAULT$, .env* - Updated outputs: .next/**, !.next/cache/**, dist/** <!-- 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 20:49:47 -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#22113
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?