github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 15:42:09 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #6061] [MERGED] chore: use relative schema path for turbo.json #6415

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6061
Author: @jslno
Created: 11/18/2025
Status: ✅ Merged
Merged: 11/18/2025
Merged by: @himself65

Base: canary ← Head: chore/relative-turbo-schema-path

📝 Commits (1)

  • 628e054 chore: use relative schema path for turbo.json

📊 Changes

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

View changed files

📝 turbo.json (+1 -1)

📄 Description

Summary by cubic

Switch turbo.json $schema to a local path (./node_modules/turbo/schema.json). This removes the external URL dependency and keeps schema validation working offline and in CI.

Written for commit 628e0545f1. 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/6061 **Author:** [@jslno](https://github.com/jslno) **Created:** 11/18/2025 **Status:** ✅ Merged **Merged:** 11/18/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `chore/relative-turbo-schema-path` --- ### 📝 Commits (1) - [`628e054`](https://github.com/better-auth/better-auth/commit/628e0545f12e1c68b3970c52847340b01db8d52d) chore: use relative schema path for turbo.json ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `turbo.json` (+1 -1) </details> ### 📄 Description <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Switch turbo.json $schema to a local path (./node_modules/turbo/schema.json). This removes the external URL dependency and keeps schema validation working offline and in CI. <sup>Written for commit 628e0545f12e1c68b3970c52847340b01db8d52d. 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 12:58:28 -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#6415
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?