Repository navigation
do not merge until @hyperdag/trustshell 1.7.0 is on npm - #58
Closed
DealAppSeo wants to merge 1 commit into
Closed
DealAppSeo wants to merge 1 commit into
DealAppSeo wants to merge 1 commit into
Conversation
…nly after npm serves it) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
Closing as superseded: #61 (merged 2026-10-23) moved BUILDERS.md to the published @hyperdag/trustshell 1.8.0, and check:builders verifies it against npm. This draft waited for 1.7.0, which was overtaken. |
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
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.
Do not merge until
npm view @hyperdag/trustshell versionreturns1.7.0. The release is trustshell #558, planned for Friday.This PR is expected to be red until then. The
BUILDERS.md matches published trustshelljob (scripts/check-builders.mjs) compares the singlePUBLISHED — \X.Y.Z`inBUILDERS.mdwithnpm view. Run locally right now, it fails with this message, as it should:npm view @hyperdag/trustshell version is 1.6.1, and BUILDERS.md says 1.7.0`. Main goes red the other way the moment 1.7.0 publishes. Merging this PR right after the publish closes that gap.Changes
BUILDERS.md: the published version (the one string the check reads) and the dated sentence about the exit-code contract, both now1.7.0. The contract itself (verify exits 0/1/2,ethersis an optional peer used bybuildX402PaymentandverifySigner) is unchanged in 1.7.0.CONTRIBUTING.md: the same published-version line, so it is not stale after the publish.Not changed
CLAUDE.md:64still says 1.6.1. It is agent configuration, so I left it to Sean.check:sdk-claimscompares README call sites against the published exports. 1.7.0 only adds exports, so it should stay green [R].🤖 Generated with Claude Code