root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(FN-2462): enforce frozen-lockfile bootstrap across workflows

Browse Source 
- Update CI, version, and test-release workflows to use pnpm install --frozen-lockfile consistently.
- Align contributor and settings documentation plus worktree init examples toward deterministic frozen-lockfile bootstrap.
- Clarify TaskExecutor worktree init guidance to distinguish dependency bootstrap failures from missing workspace dist export failures.
- Refresh workflow, executor, restart, and SettingsModal tests (including stable Node Sync tab selection) to assert the new bootstrap contract.
This commit is contained in:
Fusion
2026-04-24 11:41:10 -07:00
committed by gsxdsm
parent e480b8d411
commit 89b5b5d68c
12 changed files with 49 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/contributing.md
View File

@@ -16,7 +16,7 @@ Thanks for contributing to Fusion.
### Install dependencies
```bash
pnpm install
pnpm install --frozen-lockfile
```
### Build all packages
@@ -54,6 +54,7 @@ pnpm typecheck # workspace typechecks
Fusion codifies workspace verification as a deterministic contract:
- Use `pnpm install --frozen-lockfile` for clean bootstrap and dependency repair paths.
- `pnpm test` must be runnable in a clean worktree without requiring a prior `pnpm build`.
- This includes clean states where `packages/core/dist`, `packages/engine/dist`, and `packages/dashboard/dist` are absent.
- `pnpm verify:workspace` is the canonical pre-merge gate and runs in strict order: