Skip to content

fix: make startNewVersion script cross-platform compatible#630

Open
armorbreak001 wants to merge 1 commit into
asyncapi:masterfrom
armorbreak001:bounty/609-windows-script-fix
Open

fix: make startNewVersion script cross-platform compatible#630
armorbreak001 wants to merge 1 commit into
asyncapi:masterfrom
armorbreak001:bounty/609-windows-script-fix

Conversation

@armorbreak001

Copy link
Copy Markdown
Contributor

Fixes #609

Problem: The startNewVersion npm script used Unix shell syntax (newVersion=) which fails on Windows CMD with 'newVersion' is not recognized.

Changes:

  • package.json: Removed shell variable assignment, script now just calls node directly
  • scripts/add-new-version.js: Falls back to process.env.npm_config_new_version which npm sets automatically on all platforms

Backward compatible: Existing usage npm run startNewVersion --new-version=2.7.0 works unchanged on all platforms (Unix, Windows CMD, PowerShell).

Verification: Run npm run startNewVersion --new-version=3.0.0 on both Linux and Windows to confirm it executes without syntax errors.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] startNewVersion script fails on Windows due to Unix shell syntax

1 participant