Commit graph CultLib/scripts/test-declared-dependency-ranges.mjs
Author SHA1 Message Date
Libby
584f144f39 Range check: build each package's own tagged version too, and bump cultnet-ts to 0.4.0
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 21m29s
The declared-range check skipped a dependency's own version, so a package that gained an export while still carrying its latest tag's version passed. cultmesh-ts imported seven names cultnet-ts-v0.3.0 lacks. The check now builds that tag (through the package's own build, with repo contracts), a fixture test pins the failure, and cultnet-ts (Unreleased holds Breaking entries) is 0.4.0 with its dependents' ranges at ^0.4.0.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-12 19:51:59 +00:00
Meta Vens
245b0619b4 Declared-range check: find npm's package root on Unix as well as Windows
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-03 01:35:45 +02:00
Meta Vens
172759fd30 Declared-range check: a clone without release tags is refused rather than passing for want of releases to build
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-03 01:30:15 +02:00
Meta Vens
4f76bb9391 cultcache-ts 0.15.0; cultnet-ts and cultmesh-ts declare ^0.15.0; a check builds the tagged releases a declared range admits
cultnet-ts imports readSingleFileStore and cultmesh-ts imports schemaIdentityOf and SchemaConflictError, none of which cultcache-ts 0.14.0 exports. The new check builds each tagged release a declared range admits and requires every runtime name the dependent imports to be an export of it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-03 01:28:48 +02:00