-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Comparing changes
Open a pull request
base repository: npm/cli
base: v11.0.0
head repository: npm/cli
compare: v11.1.0
Commits on Dec 16, 2024
-
fix(search): properly display multiple search terms (#7980)
When searching for multiple terms in npm, the highlighting code has a bug where it duplicates the output any time there are matching terms. This fixes the highlighting code. Before:  After: 
Configuration menu - View commit details
-
Copy full SHA for f7da341 - Browse repository at this point
Copy the full SHA f7da341View commit details
Commits on Dec 20, 2024
-
fix(sbom): deduplicate sbom dependencies (#7992)
Certain project dependency trees may result in an SBOM with duplicate entries. This fix ensures that each unique dependency (identified by the combination of package name and version) only appears in the SBOM once. Applies to both SPDX and CycloneDX SBOM formats. Specific to the CycloneDX format, this change also removes the `cdx:npm:package:path` property from the `component` entries in the generated SBOM. Since the same package may be present at multiple paths within the project and we're now de-duplicating those packages, it no longer makes sense to include this in the SBOM. This does not impact the SPDX format as there is no equivalent property. Fixes: #6967 Signed-off-by: Brian DeHamer <bdehamer@github.com>
Configuration menu - View commit details
-
Copy full SHA for ab9ddc0 - Browse repository at this point
Copy the full SHA ab9ddc0View commit details
Commits on Jan 6, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 1764a37 - Browse repository at this point
Copy the full SHA 1764a37View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7f6c997 - Browse repository at this point
Copy the full SHA 7f6c997View commit details
Commits on Jan 14, 2025
-
docs: safer documentation urls, repos, packages (#8030)
Noticed some of the resources pointed to external sites not controlled by npm or github and wanted to clean them up so they can't be squatted on.
Configuration menu - View commit details
-
Copy full SHA for 866b5ee - Browse repository at this point
Copy the full SHA 866b5eeView commit details
Commits on Jan 17, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 7e7961d - Browse repository at this point
Copy the full SHA 7e7961dView commit details -
fix(publish): accept publishConfig.tag to override highes semver check
Setting `tag` in `publishConfig` constitutes a "non default" scenario.
Configuration menu - View commit details
-
Copy full SHA for 7f72944 - Browse repository at this point
Copy the full SHA 7f72944View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8a911ff - Browse repository at this point
Copy the full SHA 8a911ffView commit details -
Configuration menu - View commit details
-
Copy full SHA for dc31c1b - Browse repository at this point
Copy the full SHA dc31c1bView commit details
Commits on Jan 21, 2025
-
docs: depth flag default value (#8051)
documentation of `ls` command specifies that `depth` flag if not set defaults to `1` but as per code it uses 0 as default value. https://github.com/npm/cli/blob/dc31c1bdc6658ab69554adcf2988ee99a615c409/lib/commands/ls.js#L113-L116 fixes: #7979
Configuration menu - View commit details
-
Copy full SHA for e90c6fe - Browse repository at this point
Copy the full SHA e90c6feView commit details -
Configuration menu - View commit details
-
Copy full SHA for 859a71c - Browse repository at this point
Copy the full SHA 859a71cView commit details -
docs: fix typos in "package-json" (#8041)
This PR fixes small typos in the documentation for "configuring npm/package-json"
Configuration menu - View commit details
-
Copy full SHA for f1af61f - Browse repository at this point
Copy the full SHA f1af61fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 215ebe4 - Browse repository at this point
Copy the full SHA 215ebe4View commit details -
Configuration menu - View commit details
-
Copy full SHA for a65e5ce - Browse repository at this point
Copy the full SHA a65e5ceView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9473a86 - Browse repository at this point
Copy the full SHA 9473a86View commit details -
Configuration menu - View commit details
-
Copy full SHA for 18e0449 - Browse repository at this point
Copy the full SHA 18e0449View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7ddfbad - Browse repository at this point
Copy the full SHA 7ddfbadView commit details
Commits on Jan 22, 2025
-
fix(publish): honor force for no dist tag and registry version check (#…
Configuration menu - View commit details
-
Copy full SHA for 31455b2 - Browse repository at this point
Copy the full SHA 31455b2View commit details -
docs: update readme for Node.js versions, remove badges (#8055)
Update the copy for "requirements" to specify that it is the Node.js support lifecycle that is key, not a specific version. Also removed the badges from the readme. Most of that info is already on the page as parsed by GitHub.
Configuration menu - View commit details
-
Copy full SHA for 3644e79 - Browse repository at this point
Copy the full SHA 3644e79View commit details -
chore: smoke tests using a preid (#8056)
#8054 broke the smoke test because were publishing the current version in a test
Configuration menu - View commit details
-
Copy full SHA for aa202e9 - Browse repository at this point
Copy the full SHA aa202e9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9281ebf - Browse repository at this point
Copy the full SHA 9281ebfView commit details
Commits on Jan 27, 2025
-
chore: stop publish smoke from check git clean (#8058)
Im a big proponent of scripts working the same way in ci as they would locally. and that we should be able to run anything the ci does locally. The publish script is used to publish npm and ws packages, but also within a series of smoke tests. Making the flags clear it's either one of the two paths was my goal.
Configuration menu - View commit details
-
Copy full SHA for 6d0f46e - Browse repository at this point
Copy the full SHA 6d0f46eView commit details
Commits on Jan 29, 2025
-
chore: splits out smoke-tests from publish-dryrun tests (#8069)
This removes the `publish.sh --smoke-publish` like from the current `smoke-publish-test.sh` (renaming it to `smoke-test.sh`) and runs both operations as seperete jobs within the `ci.yml` (on pr) and `ci-release.yml` (on merge) workflow. Why? To avoid changed files / git dirty issues from one operation to the next. With this PR we should have the same checks that merge has, on pr as well, preventing scenarios where a PR breaks a `smoke test` or `publish --smoke-publish` test. The only difference between merge / pr is that merge has more tested node versions, if PRs start to pass but fail in these version lets add the full matrix. ```sh npm i npm@latest -g && node scripts/git-dirty.js && node scripts/resetdeps.js && ./scripts/smoke-tests.sh ``` ```sh npm i npm@latest -g && node scripts/git-dirty.js && node scripts/resetdeps.js && node ./scripts/publish.js --pack-destination=${pwd} --smoke-publish=true ```
1Configuration menu - View commit details
-
Copy full SHA for 61f00e3 - Browse repository at this point
Copy the full SHA 61f00e3View commit details -
Configuration menu - View commit details
-
Copy full SHA for cab74ff - Browse repository at this point
Copy the full SHA cab74ffView commit details
There are no files selected for viewing