Prevent release dry runs from publishing through npm shims - #3
Merged
Conversation
flujo-app
marked this pull request as ready for review
September 6, 2026 03:24
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
1 participant
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.
PowerShell's npm shim can consume --dry-run and expose it only as npm_config_dry_run=true, leaving the release script with no arguments and causing a real patch release. Honor that setting before preflight, reject unknown options and multiple version arguments, and make help exit before any Git or publication commands. Normal release version selection remains unchanged.
Validation: all 14 real-entrypoint tests pass on Windows and Ubuntu in workflow 34005260591. Child-process APIs are intercepted so dry-run/help/invalid arguments cannot execute publication or Git mutations. Syntax and whitespace checks pass. The added CI workflow runs these checks on pull requests and does not publish artifacts.
This change keeps Brain at 0.3.15. Its main-branch image workflow will complete that existing release using the now-published and verified FLUJO 3.45.2. FLUJO's public npm consumer, full test gate, tagged Windows consumer, regular container and dedicated worker gates all passed before this merge.