[pull] latest from npm:latest by pull[bot] · Pull Request #109 · LadyK-21/cli

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z

⚠️Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

pull · 2025-12-01T18:25:03Z

See Commits and Changes for more details.

Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Summary This PR clarifies the documentation for `npm version` to explicitly describe its behavior when the current version is a prerelease version. ## Problem The current documentation states that when using `patch`, `minor`, or `major` arguments, "the existing version will be incremented by 1 in the specified field." However, this is incomplete and misleading when the current version is a prerelease. When the current version is a prerelease (e.g., `1.2.0-5`), running `npm version patch` (or `minor`/`major`) will simply remove the prerelease suffix without incrementing the version number. The result would be `1.2.0`, not `1.2.1`. This undocumented behavior has led to: - Developer confusion when the version doesn't increment as expected - Incorrect guidance from LLMs trained on the incomplete documentation ## Solution Added a note immediately after the existing sentence to clarify this behavior: > **Note:** If the current version is a prerelease version, `patch`, `minor`, and `major` will simply remove the prerelease suffix without incrementing the version number. For example, `1.2.0-5` becomes `1.2.0` with `npm version patch`, not `1.2.1`. ## Testing The documentation change is straightforward and doesn't affect code behavior. The example provided matches the actual behavior of the `semver.inc` function from the node-semver package. Fixes#8637

## Description This PR clarifies that the `--tag` option for `npm install` only applies to packages specified on the command line, and does not override version ranges in `package.json`. ## Changes - Added a note explaining that `--tag` does not affect dependencies listed in `package.json` - Explained that version ranges in `package.json` take precedence over the `--tag` flag - Provided an example showing the correct way to install a tagged version: `npm install foo@beta` ## Context Users were confused when `npm install --tag beta` didn't install beta-tagged versions of dependencies listed in `package.json`. The issue reporter discovered that when `package.json` specifies a version range like `"^0.3.0"`, the `--tag` flag is ignored and npm installs a version matching the range, even if the `beta` tag points to a different version (like `0.4.0-beta.1`). This was marked as needing better documentation/logging to make the behavior less surprising. Closes#4685 Co-authored-by: Max Black <husivm@google.com>

LadyK-21 · 2025-12-01T18:25:33Z