📦 deps(thirdparty): update snapshots
This commit is contained in:
@@ -72,8 +72,8 @@ To add a scenario: append to the `evals` array with the next sequential `id` and
|
||||
## Development Commands
|
||||
|
||||
```bash
|
||||
npm run bump # Propagate the package.json version to all manifests + README badge (NOT changelog)
|
||||
npm run validate # Repo consistency: manifests, README badge, changelog, source inventory, skills structure
|
||||
npm run bump # Propagate the package.json version to all manifests + every version-bearing text file (NOT changelog)
|
||||
npm run validate # Repo consistency: manifests, version refs, changelog, source inventory, skills structure
|
||||
npm test # Unit tests for validate-repo helpers
|
||||
npm run evals # Eval structural validation (IDs, fields, risk-code refs)
|
||||
npm run evals:live # Live evals against the AI (requires ANTHROPIC_API_KEY)
|
||||
@@ -87,4 +87,4 @@ CLAUDE_PLUGIN_ROOT=1 bash hooks/session-start # plugin platform branch
|
||||
|
||||
## Release Process
|
||||
|
||||
Set the new version in `package.json` (e.g. `npm version <v> --no-git-tag-version`), then `npm run bump` (propagates the version to all manifests + README badge) → add the new `CHANGELOG.md` section by hand → `npm run validate` → commit, push, tag GitHub release.
|
||||
Set the new version in `package.json` (e.g. `npm version <v> --no-git-tag-version`), then `npm run bump` (propagates the version to all manifests plus every version-bearing text file listed by `scripts/version-refs.mjs` — all six README badges and the docs landing-page JSON-LD) → add the new `CHANGELOG.md` section by hand → `npm run validate` → commit, push, tag GitHub release.
|
||||
|
||||
Reference in New Issue
Block a user