Skip to content

fix(builders): name trustshell 1.6.1, and read the checked version from the doc - #52

Merged
DealAppSeo merged 2 commits into
mainfrom
claude/2026-10-14-builders-161
Oct 14, 2026
Merged

DealAppSeo merged 2 commits into
mainfrom
claude/2026-10-14-builders-161

Conversation

@DealAppSeo

Copy link
Copy Markdown
Owner

Why now

npm serves @hyperdag/trustshell 1.6.1. scripts/check-builders.mjs hardcoded 1.6.0 twice, so it fails on main today:

check:builders — FAILED
  npm view @hyperdag/trustshell version is 1.6.1, and BUILDERS.md says 1.6.0

That check is the blocking CI job "BUILDERS.md matches published trustshell". Main last ran CI on 10-12, before 1.6.1 shipped, so it still looks green. The next PR here would go red for a reason unrelated to it.

Fix

  • Checker: it now reads the version BUILDERS.md names (exactly one PUBLISHED — \x.y.z``) and compares that with npm. A publish still turns CI red until the doc is updated, which is the intended tripwire, but the checker never needs editing again. Hardcoding the version is what made it a code edit every release.
  • BUILDERS.md: names 1.6.1, and §1a documents the votes field the live classify reply now returns.

Re-measured on 1.6.1, 2026-10-14

  • npm view: trustshell 1.6.1; @hyperdag/protocol, identity-erc8004, reputation-zkp still 404.
  • trustshell verify from a clean install: Paris → exit 0, an unverifiable private claim → exit 2, Eiffel/Rome → exit 1.
  • ethers ^6.14.0 is still an optional peer (peerDependenciesMeta).
  • packages/interfaces still has no commits on main.
  • The §1a curl, verbatim: {"label":"pass","by":"votes","voters":["groq","cerebras"],"deciders":[…],"votes":[{"voter":"groq","family":"gpt-oss","verdict":"TRUE"},…]}.

Checker evidence

VERIFIED as committed · FAILED when the doc names 1.6.0 · FAILED when it names two versions.

🤖 Generated with Claude Code

…om the doc

npm now serves @hyperdag/trustshell 1.6.1. check:builders hardcoded 1.6.0 twice,
so it FAILS on main today (measured locally) and the blocking "BUILDERS.md
matches published trustshell" job would turn the next PR in this repo red for a
reason unrelated to it. main last ran CI on 10-12, before 1.6.1 shipped.

- check-builders.mjs reads the version BUILDERS.md names (exactly one
  "PUBLISHED — `x.y.z`") and compares THAT with npm. A publish still turns CI
  red until the doc is updated, but the checker never needs editing again.
- BUILDERS.md names 1.6.1. Re-measured on 1.6.1 2026-10-14: `trustshell verify`
  exits 0 / 1 / 2 for PASS / VETO / NOT_CHECKED, ethers is still an optional
  peer, the other packages still 404, the six-interface kernel still not on
  main, and the section 1a curl still returns pass.
- section 1a documents the `votes` field the live classify reply now carries.

Checker: VERIFIED as committed; FAILED when the doc names 1.6.0; FAILED when
it names two versions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@strix-security

strix-security Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Strix Security Review

No security issues found.

Review summary

Reviewed all five changed files. The PR is a documentation/version-bump plus a refactor of the CI checker scripts/check-builders.mjs to read the published trustshell version from BUILDERS.md instead of hardcoding it. The checker uses execFileSync with fixed literal arguments (no shell interpolation of untrusted input), a simple non-catastrophic regex, and a plain string-equality comparison against npm view output — no injection, secrets, auth, or crypto concerns. The documentation edits (BUILDERS.md, CLAUDE.md, CONTRIBUTING.md, README.md) are version updates and clarifications with no security impact. No security vulnerabilities were found in the changed code.

Updated for d0b88e0.


Reviewed by Strix
Re-run review · Configure security review settings

README told an outside builder to `npm i -g @hyperdag/trustshell@1.6.0` in two
places, which installs the old release (no my_job, no kernel client) now that
npm serves 1.6.1. The install commands are unpinned: a pinned install goes
stale on every publish, which is how this happened. The measured version lives
in BUILDERS.md, under check:builders. CLAUDE.md and CONTRIBUTING.md now say
1.6.1 (measured 2026-10-14).

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

Copy link
Copy Markdown
Owner Author

Added a second commit with the same theme: README.md told outside builders to npm i -g @hyperdag/trustshell@1.6.0 in two places (installs the old release now that npm serves 1.6.1). Those install lines are now unpinned, so they can't go stale on the next publish; the measured version stays in BUILDERS.md under check:builders. CLAUDE.md and CONTRIBUTING.md now say 1.6.1.

@DealAppSeo
DealAppSeo merged commit a5d3016 into main Oct 14, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant