Repository navigation
First run: warn on older Node instead of refusing, and show what failed - #17
Merged
Merged
Conversation
Anyone on a Node 22 or 24 below the October 2026 security release got exit 2 and nothing else. The floors are now each line's first release with node:sqlite and no flag (22.13.0, 24.0.0); below the security release the launcher warns and doctor shows [warn]. The demo was run on 22.13.0, 24.0.0, 24.18.0 and 24.22.2 with the same counts. assess now writes a summary to stderr: each check that did not pass and how to see the findings. stdout is unchanged. Observed values appear only for the owned synthetic fixture, so a real app's values stay out of CI logs, and control characters are stripped. Rename the root action so it reads clearly in Marketplace search. Signed-off-by: YusefSyed <211442445+YusefSyed@users.noreply.github.com>
- Raise the 22 floor to 22.16.0: on 22.13.0 node:sqlite ignores the open timeout (PRAGMA busy_timeout reads 0), so the observers' lock fallback would not wait. - A run that exits 1 with every check passed now says why, and not-applicable rows are counted. - The export hint now works as printed: it writes into the evidence directory. - core-practice's why() prefers row reasons, since assess now always writes stderr. - DEPENDENCIES no longer says 24.18.0 is refused. Signed-off-by: YusefSyed <211442445+YusefSyed@users.noreply.github.com>
The escaped form was written as a literal line separator, which broke the regex literal. Signed-off-by: YusefSyed <211442445+YusefSyed@users.noreply.github.com>
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 changes
node:sqliteneeds no flag and honours the open timeout the observers use. Below the October 2026 security release (22.23.4 or 24.22.1) the launcher warns and runs, anddoctorshows[warn]. Before this, those versions got exit 2 and nothing ran.assessoutput: a summary on stderr lists each check that did not pass, anything else keeping the run from being clean, and an export command that works as printed. stdout JSON is unchanged. Observed values appear only for the owned synthetic fixture, so a real app's values stay out of CI logs. Control characters are stripped.ScopeHaven - check what an AI agent did, for Marketplace search.The failing case
A fresh clone on Node 24.18.0:
./scopehaven assess --target demo-vulnerableexited 2 and ran nothing.Checked
On macOS arm64, official builds with verified checksums: 22.16.0, 24.0.0, 24.18.0 and 24.22.2 each gave
doctorready, demo-vulnerable exit 1 with 26 failures, demo-repaired exit 0. 22.13.0 is refused with exit 2: itsnode:sqlitereadsbusy_timeoutas 0 where 22.16.0 and 24.0.0 read 2000.Limits
The suite itself runs on the pinned 24.22.2. Older versions were checked with
doctorand both demo targets, not the full suite, and CI does not run them. A below-floor run goes ahead with only a warning.🤖 Generated with Claude Code