ci: release and cache v5 from the v5 branch

[adrians5j]

What changed

v5 maintenance moves to a single v5 branch (created from v5-dev), replacing v5-dev and v5-next. The workflows on next that target v5 now use it:

• 📦 v5 Custom Release checks out v5.
• Rebuild Global Cache ("v5" branch) (rebuildGlobalCacheV5.yml) checks out v5 and writes the v5-… key under v5/. The v5 PR workflows build their cache key and path from the PR's base branch, so PRs into v5 restore this cache, the same as with v5-dev before.
• Removed v5_rebuildGlobalCacheDev.yml, v5_rebuildGlobalCacheNext.yml and their frozen wac source. They checked out v5_dev and v5_next (underscores), branches that don't exist, and failed on every nightly run. rebuildGlobalCacheV5.yml already covers the v5 cache.

The v5 branch itself carries one change on top of v5-dev: (v5) Push triggers on pushes to v5 instead of v5-next/v5-dev.

yarn ci-workflows:build regenerates the remaining workflows with no other changes.

Workspace: wby-next3 · 🐛 release wflows cleanup

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated release and cache automation to use the v5 branch instead of v5-dev.
  • Removed the scheduled cache rebuild workflows for the development and next branches.
  • Release version validation, distribution tag selection, and publishing behavior remain unchanged. These updates affect release and build automation; no end-user features or interface changes are included.

[github-actions]

🚓 Slop Cop

✅ Nothing worth flagging. The diff looks consistent with the PR's stated intent and the code-style rules.

PR is a coherent CI-only change that matches its stated intent: it repoints v5 release/cache workflows to the new v5 branch and removes two dead/broken workflows (and their frozen wac source) that referenced nonexistent branches.

_{Automated, non-blocking heads-up from an LLM. It can be wrong — use your judgment. Regenerates on every push.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3ade7445-c978-4b40-bdf2-f8163bfa35bb

📥 Commits

Reviewing files that changed from the base of the PR and between a14df6a and a98be0a.

📒 Files selected for processing (5)

• .github/workflows/rebuildGlobalCacheV5.yml
• .github/workflows/v5_customRelease.yml
• .github/workflows/v5_rebuildGlobalCacheDev.yml
• .github/workflows/v5_rebuildGlobalCacheNext.yml
• .github/workflows/wac/v5_rebuildGlobalCache.wac.frozen.ts

💤 Files with no reviewable changes (3)

• .github/workflows/v5_rebuildGlobalCacheDev.yml
• .github/workflows/v5_rebuildGlobalCacheNext.yml
• .github/workflows/wac/v5_rebuildGlobalCache.wac.frozen.ts

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 2 remain after this review.

📝 Walkthrough

The active global cache and custom release workflows now target the v5 branch. The v5_dev and v5_next global cache workflows and their exported workflow configurations were removed.

Changes: v5 workflow alignment

Layer / File(s)	Summary
Update active v5 workflows .github/workflows/rebuildGlobalCacheV5.yml, .github/workflows/v5_customRelease.yml	The cache workflow now checks out and builds v5 and uses a v5- cache key. The custom release workflow checks out v5.
Remove branch-specific cache workflows .github/workflows/v5_rebuildGlobalCacheDev.yml, .github/workflows/v5_rebuildGlobalCacheNext.yml, .github/workflows/wac/v5_rebuildGlobalCache.wac.frozen.ts	The v5_dev and v5_next cache workflows and their exported workflow configurations were removed.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to a98be

The v5 workflows align on the cache key and path, and v5 PRs can access the cache through the default-branch scope. No material merge blocker is identified.

Pre-merge checks · 5

Passed checks (5 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly summarizes the main change: updating CI release and cache workflows to use the v5 branch.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}