ee9c832e93
Stamps `## Unreleased` as `## 0.1.1 — 2026-07-19` and re-arms the changelog with a fresh, empty `## Unreleased` above it — both halves in this diff, per CONTRIBUTING's ceremony (#113/#114; heavy-duty/rig#66). Bumps package.json and package-lock.json 0.1.1-dev -> 0.1.1. Patch is correct: the shipped section carries only `### Fixed`. This is the first cast release to go through the merge door. 0.1.0 could not — the interlock refused it (run 29698017907) because cast had said `0.1.0` since its first commit, so there was no `-dev` transition to detect, and it shipped by the manual tag path. main now genuinely reads `0.1.1-dev`, so release.yml's decide step sees bare-and-changed: the ceremony state. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
24 lines
524 B
JSON
24 lines
524 B
JSON
{
|
|
"name": "cast",
|
|
"version": "0.1.1",
|
|
"type": "module",
|
|
"private": true,
|
|
"engines": { "node": ">=22.12.0" },
|
|
"bin": { "cast": "./dist/cli.js" },
|
|
"scripts": {
|
|
"build": "tsc",
|
|
"test": "vitest run",
|
|
"format": "biome format --write .",
|
|
"check": "biome check --error-on-warnings ."
|
|
},
|
|
"dependencies": {
|
|
"yaml": "^2.5.0",
|
|
"zod": "^3.25.76"
|
|
},
|
|
"devDependencies": {
|
|
"@biomejs/biome": "^1.9.0",
|
|
"@types/node": "^22.10.0",
|
|
"typescript": "^5.7.0",
|
|
"vitest": "^2.1.0"
|
|
}
|
|
}
|