chore: update GitHub actions to Node 24 runtime

[AmanVarshney01]

Summary

• Update checkout and setup-node actions to v6 across release, preview, and test workflows.
• Disable setup-node package manager cache for deterministic CI/release runs.
• Keep npm trusted publishing behavior unchanged.

Verification

• git diff --check
• pre-commit hook ran bun check

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow versions to the latest major releases for improved security and stability.
  • Optimized build pipeline caching configuration across CI/CD workflows.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
create-better-t-stack-web	Ready	Preview, Comment	May 25, 2026 7:43am

[coderabbitai]

Walkthrough

This PR upgrades GitHub Actions to newer major versions across three CI/CD workflows. actions/checkout and actions/setup-node are bumped from v4 to v6 in all workflows. The test and release workflows additionally explicitly disable package manager caching via package-manager-cache: false.

Changes

GitHub Actions Version Upgrades

Layer / File(s)	Summary
Workflow action version upgrades .github/workflows/pr-preview.yaml, .github/workflows/release.yaml, .github/workflows/test.yaml	actions/checkout and actions/setup-node upgraded to v6 across all three workflows. Release and test workflows add explicit package-manager-cache: false configuration; pr-preview workflow preserves existing node setup parameters.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title mentions updating GitHub actions to Node 24 runtime, but the actual changes only update action versions (checkout and setup-node to v6) without explicit evidence of Node 24 runtime adoption in the diffs.	Clarify whether the title should reference the action version upgrades or confirm Node 24 runtime is the actual outcome of updating to actions v6.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 35092f6c-8d58-4051-8eb5-db2c0d297088

📥 Commits

Reviewing files that changed from the base of the PR and between e521766 and 7641f60.

📒 Files selected for processing (3)

• .github/workflows/pr-preview.yaml
• .github/workflows/release.yaml
• .github/workflows/test.yaml