chore: sync develop with the v7.17.4 release - #9
Merged
Merged
Conversation
Bumps package.json and hooks/installer VERSION to 7.17.4 and regenerates the tracked .husky hooks. schemaVersion stays 2. Ships the fix already on develop: `ruleofcode init` died with an ERR_USE_AFTER_CLOSE stack trace wherever there was no terminal to answer its prompts — CI, a container, a pipe — which is precisely the command the site tells new users to run. It now falls back to the documented `--quick` defaults and says so, refuses to overwrite an existing config it cannot ask about, and still honours --force. No verdict change: init writes configuration, it does not judge code. Gate: eslint 0, 502 suites / 13857 tests (jest exit 0), canary green (py100/ng136/node78). Self-audit: passed 35, failed 0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Release/v7.17.4
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 this changes
Verdict impact
(then: state the before/after values and what a consumer must do)
Evidence
tests/detectionLimitsupdated if what the detector cannot see has changedGate
npm run lint— 0 errorsnpx jest— full suite greennpm run canary— red/green proven across stacksnode dist/cli.js audit— RuleOfCode still passes its own lawNotes for the reviewer