chore(0.31.1): republish — fix stale dist on v0.31.0 npm artifact#68
Merged
Conversation
Pin ws to ^8.20.1 via pnpm override to close GHSA-58qx-3vcg-4xpx (CVE-2026-45736, "Uninitialized memory disclosure", medium severity). ws is a transitive dependency pulled by viem (peer of @tangle-network/tcloud and @tangle-network/sandbox). Direct deps do not expose ws, so the fix is applied via pnpm.overrides rather than a direct-dep bump. Versions: - ws: 8.18.3 -> 8.20.1 (vulnerable range was >=8.0.0 <8.20.1) Verification: typecheck + 1220 tests + build all green.
The v0.31.0 tag's published tarball shipped a dist/ predating the source merge for JudgeScoresRecord. dist/index.d.ts was missing the type re-export and dist/index.js was missing the `recordOutcome.judgeScores = outcome.judgeScores` propagation line in the campaign runner — even though the tagged commit had both. Consumers that bumped to ^0.31.0 got a typecheck failure on RunOutcome.judgeScores and a silent drop on the wire. No source change beyond the version bump. The retag forces a clean pnpm build and republish. Post-republish verification: - dist/index.d.ts contains JudgeScoresRecord - dist/index.js carries the recordOutcome.judgeScores assignment - pnpm typecheck + pnpm test clean (1220/1220)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v0.31.0 tag's published tarball shipped a stale
dist/predating the source merge forJudgeScoresRecord:dist/index.d.tsmissing the type re-export → consumerpnpm install @tangle-network/agent-eval@0.31.0typecheck-fails onRunOutcome.judgeScoresdist/index.jsmissing therecordOutcome.judgeScores = outcome.judgeScorespropagation line → silent drop on the wire even when consumers worked around the typeCause: a build artifact picked up by the publish workflow predated the source merge for #66, even though the tagged commit
51f6e74has the right source. Reproducing the workflow locally (git clone,git checkout v0.31.0,pnpm install --frozen-lockfile,pnpm build) produces a correctdist/index.d.ts. The published artifact does not match. Likely a stale cacheddist/was bundled by the publish step.No source change beyond the version bump. The retag forces a clean rebuild + republish.
Verified post-build
dist/index.d.tscontainsJudgeScoresRecord✓dist/index.jscarriesrecordOutcome.judgeScores = …end-to-end propagation ✓pnpm typecheck && pnpm testclean (1220/1220) ✓__init__.py) ✓After merge: tag
v0.31.1to trigger the publish workflow, then bump@tangle-network/agent-eval ^0.31.0 → ^0.31.1in any consumer that relies onJudgeScoresRecord(agent-builder is the only known consumer today; will land as a follow-up bump after publish completes).