Raise @novox/mesh-sdk to 0.1.17, and a unit test refuses a packed change that keeps its version (issue 1899, met twice) #75

2026-10-23T22:27:27Z

mesh-tools commented

2026-10-23 22:27:27 +00:00

Fixes issue 1899, met a second time 2026-10-24 00:10: the delivery of the 1930 group (plan-1792793288246081287) failed at mesh-sdk's build, 'version taken: @novox/mesh-sdk@0.1.16: the registry holds another sha512'. R4g's 232ded26 changed package.json's scripts (packed) without raising the version; the check named at the first meeting was never built.

package.json, package-lock.json: 0.1.17.
go/packageguard/packageversion_test.go + package-version.sum: a sha256 over what npm packs (package.json without its version, src/, tsconfig.json, README.md) beside the version; the unit test fails when those inputs change while the version stays ('Raise @novox/mesh-sdk's version and update package-version.sum'), and when the sum's version is stale. UPDATE_PACKAGE_VERSION_SUM=1 go test regenerates it. No network, ~6 ms.

Tests: fails on main 53a1de2a (inputs changed since 0.1.16), passes here. Unit suite, go vet -tags integration and the local integration level green. No try waited for (operator 2026-10-24 00:24: build, publish, deliver until the new setup works).

Moves mesh-sdk (its package to the registry). Hardening (the lock's typescript, lock/package version agreement, eol) is note 5 on 1899.

Reviewed-by: review-1899@shanks at 35e86b00d3
Pushed-by: fix-1899@shanks

Fixes issue 1899, met a second time 2026-10-24 00:10: the delivery of the 1930 group (plan-1792793288246081287) failed at mesh-sdk's build, 'version taken: @novox/mesh-sdk@0.1.16: the registry holds another sha512'. R4g's 232ded26 changed package.json's scripts (packed) without raising the version; the check named at the first meeting was never built. - package.json, package-lock.json: 0.1.17. - go/packageguard/packageversion_test.go + package-version.sum: a sha256 over what npm packs (package.json without its version, src/, tsconfig.json, README.md) beside the version; the unit test fails when those inputs change while the version stays ('Raise @novox/mesh-sdk's version and update package-version.sum'), and when the sum's version is stale. `UPDATE_PACKAGE_VERSION_SUM=1 go test` regenerates it. No network, ~6 ms. Tests: fails on main 53a1de2a (inputs changed since 0.1.16), passes here. Unit suite, go vet -tags integration and the local integration level green. No try waited for (operator 2026-10-24 00:24: build, publish, deliver until the new setup works). Moves mesh-sdk (its package to the registry). Hardening (the lock's typescript, lock/package version agreement, eol) is note 5 on 1899. Reviewed-by: review-1899@shanks at 35e86b00d3f089f84278c41465fd9635b85b1290 Pushed-by: fix-1899@shanks

mesh-tools added 1 commit 2026-10-23 22:27:27 +00:00

Raise @novox/mesh-sdk to 0.1.17 and guard that a changed package carries a new version (issue 1899)

mesh/delivery delivered

Details

mesh/check checking 35e86b00d3f0 on e1f393bbb12e

35e86b00d3

mesh-tools commented

2026-10-23 22:27:35 +00:00

Delivery novox/mesh-sdk@35e86b00d3f0 — delivered since 2026-10-23T22:37:02Z

Delivery plan — builds mesh-sdk, sent nowhere; no bus step

tier 0: mesh-sdk

Machines

mesh-sdk on every machine running it: sent

Transitions

2026-10-23 22:27 (new) → proposed (announced): novox/mesh-sdk#75's head announced
2026-10-23 22:35 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
2026-10-23 22:36 held → delivering (release): the operator's hand merge at 00:35, which by the operator's word of 2026-10-24 00:24 releases it (build, publish, deliver until the new setup works); reviewed at its head
2026-10-23 22:37 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-sdk@35e86b00d3f0` — **delivered** since 2026-10-23T22:37:02Z **Delivery plan** — builds mesh-sdk, sent nowhere; no bus step - tier 0: mesh-sdk **Machines** - mesh-sdk on every machine running it: sent **Transitions** - 2026-10-23 22:27 (new) → proposed (announced): novox/mesh-sdk#75's head announced - 2026-10-23 22:35 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-23 22:36 held → delivering (release): the operator's hand merge at 00:35, which by the operator's word of 2026-10-24 00:24 releases it (build, publish, deliver until the new setup works); reviewed at its head - 2026-10-23 22:37 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben merged commit e1f393bbb1 into main

2026-10-23 22:35:43 +00:00

jschoubben deleted branch fix/1899-version-guard

2026-10-23 22:35:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-sdk#75