Repository navigation
Conversation
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
This branch has not been deployed
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.
What
hyperframes add <tag>now reports an incomplete installation as a failure. Scripts and agents receive exit code 1 andok: falsewhen any block fails; JSON includes each failed block's name and error. Successful installations remain available.Why
The tag loop catches each install error and then reports unconditional success. In JSON mode, it also drops every failure reason.
The same real source CLI process with fixture HTTP responses:
ok: true; no files; no errorsok: false; named HTTP 404 errorok: trueok: false; successful HTML preservedok: trueok: true;errors: []The issue includes a self-contained reproduction. Only HTTP responses are fixtures; dispatch, resolution, installation, filesystem writes and process exit handling use the real implementation.
Related work
Fixes #6084.
#4432 preserves warnings from successful installs. Open #5256 refreshes item manifests during discovery; neither handles failed file installation.
How
Collect per-item errors, derive JSON status from the collection and use the existing command-failure boundary after the batch finishes. The human summary marks incomplete installs as an error. Document the exit status and JSON fields.
Test plan
Validated on main
10c724bf5, Linux x86_64, Node 26.11.1, Bun 1.4.1 (repository pins 1.4.4), and Citty 0.2.2. CLI TypeScript checking reports a missing installed@aws-sdk/s3-request-presignerdependency through AWS Lambda source and no changed-file type errors. Full workspace checks have the same dependency limitation;mintis absent, so full docs validation was not run.