fix: remove shell setting for wizer call#303
Merged
vados-cosmonic merged 1 commit intobytecodealliance:mainfrom Oct 8, 2025
Merged
fix: remove shell setting for wizer call#303vados-cosmonic merged 1 commit intobytecodealliance:mainfrom
vados-cosmonic merged 1 commit intobytecodealliance:mainfrom
Conversation
This commit removes the `shell: true` configuration for the Wizer call, as it triggers a warning with more recent NodeJS versions, due to attempting to pass options to an spawned command when `shell: true`.
tschneidereit
approved these changes
Oct 8, 2025
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.
This commit removes the
shell: trueconfiguration for the Wizer call, as it triggers a warning with more recent NodeJS versions, due to attempting to pass options to an spawned command whenshell: true...For reference the deprecation warning looks like this:
We don't actually use user submitted args directly so we weren't really at risk of this, but better to have this not show up.