cultnet-ts 0.4.0 release notes, range check in the npm publish gate, fixture closes build-path gaps #146

Merged

libby merged 1 commit from hands/cultnet-040-release into main 2026-11-12 21:21:42 +00:00

Conversation 0 Commits 1 Files changed 6 +35 -12

libby commented 2026-11-12 20:54:59 +00:00

Member

Copy link

Follow-up cultlib-gaps:follow_up:cultnet-ts-040-release-notes.

• cultnet-ts CHANGELOG: Unreleased becomes [0.4.0]; cultmesh-ts and cultmesh-browser Unreleased record the range move to ^0.4.0.
• scripts/release-after-suite.mjs: an npm tag release builds the workspace and runs test-declared-dependency-ranges.mjs after the semver check and before the package's tests (the workflow's pinned release step is unchanged; the gate is inside the one process).
• Fixture test: package a now generates a module from repo contracts/ in its build, so swapping npm run build for bare tsc, or dropping contracts from the tag archive, fails it (both mutations checked red).

check-changelog-semver.test.mjs: 54 of 84 pass in the Mind sandbox only because dotnet cannot create its first-use directory under the read-only HOME; with a writable HOME/DOTNET_ROOT (dnenv.sh) all 84 pass at this head, including the updated release-after-suite test. Sandbox, not a bug.

🤖 Generated with Claude Code

Follow-up `cultlib-gaps:follow_up:cultnet-ts-040-release-notes`. - `cultnet-ts` CHANGELOG: Unreleased becomes `[0.4.0]`; `cultmesh-ts` and `cultmesh-browser` Unreleased record the range move to `^0.4.0`. - `scripts/release-after-suite.mjs`: an npm tag release builds the workspace and runs `test-declared-dependency-ranges.mjs` after the semver check and before the package's tests (the workflow's pinned release step is unchanged; the gate is inside the one process). - Fixture test: package `a` now generates a module from repo `contracts/` in its build, so swapping `npm run build` for bare tsc, or dropping `contracts` from the tag archive, fails it (both mutations checked red). `check-changelog-semver.test.mjs`: 54 of 84 pass in the Mind sandbox only because dotnet cannot create its first-use directory under the read-only `HOME`; with a writable `HOME`/`DOTNET_ROOT` (`dnenv.sh`) all 84 pass at this head, including the updated release-after-suite test. Sandbox, not a bug. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

libby added 1 commit 2026-11-12 20:54:59 +00:00

cultnet-ts 0.4.0 release notes; npm publish gate runs the declared-range check; fixture builds like cultnet-ts ... 4fb07ab3bb

cultnet-ts's Unreleased section becomes [0.4.0]; cultmesh-ts and cultmesh-browser record the move to cultnet-ts ^0.4.0. release-after-suite builds the workspace and runs the range check for an npm tag release, before the package's tests. The fixture package generates a module from repo-level contracts/, so a tag built by a bare tsc or archived without contracts/ fails it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

libby merged commit 1045914701 into main 2026-11-12 21:21:42 +00:00

libby referenced this pull request from a commit 2026-11-12 21:21:43 +00:00

cultnet-ts 0.4.0 release notes, range check in the npm publish gate, fixture closes build-path gaps (#146)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

GameCult/CultLib!146

No description provided.