chore(fleet): re-cascade to resolve wheelhouse lock-step mismatch - #1506
Merged
Merged
Conversation
The pinned fleet-pack release and the cascaded template SHA had drifted out of lock-step, blocking scripts/fleet from materializing locally. Re-cascading pulls in catalog bumps (oxlint, oxfmt, taze, chrome-devtools-mcp, and others past their soak window) and syncs the drifted fleet scaffolding to the current template.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fleet-pack release and the cascaded template SHA had drifted out of lock-step, which blocked scripts/fleet from materializing locally. Re-cascading fixes it and pulls in a few soaked catalog bumps along the way.
Verification
I ran the sync-scaffolding cascade with --fix, then ran pnpm install to confirm the lockfile resolves cleanly.Note
High Risk
Touches CI checkout, toolchain install, artifact/cache clients, and integrity verification for downloaded binaries. A bug here can break installs, skip quality gates on backup refs, or ship unverified tools.
Overview
Re-cascades the fleet pack (
bundle.ref/cascadeSha→d5cde643…) so localscripts/fleetcan materialize again, and pulls soaked tool bumps (pnpm11.21.0,uv0.12.4,sfw1.15.0) plus Windows platform keys (win32-*) and explicitoriginfields.Supply-chain / CI: Toolchain installs (Chrome, rustup, Go) now resolve pinned assets, SRI-verify bytes, then live-check publisher checksums and pin age before extract. Workflows drop
actions/checkout,setup-go,cache, andupload-artifactin favor of first-party fleet composites (checkout,setup-go-toolchain, cache restore/save,upload-artifact/download-artifact).pnpm installalways passes--frozen-lockfileor--no-frozen-lockfileso CI cannot silently freeze a half-hydrated tree.Local/dev: Statusline prefers a native binary with Node fallback. Vitest worker count scales with cores (cap 24). New git-hook helpers block non-cascade edits of fleet-canonical paths and skip quality gates on
wip//worktree/backup pushes.ci:localmoves off@redwoodjs/agent-citorun-local-ci.Reviewed by Cursor Bugbot for commit c598f02. Configure here.