-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pull] latest from npm:latest #6
base: latest
Are you sure you want to change the base?
Conversation
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
1 similar comment
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
24 similar comments
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
The rtd-bot is activated, but no .github/config.yml found in this repository. |
BREAKING CHANGE: `bun.lockb` files are now included in the strict ignore list during packing
Adds bun lockfile, and points to the package.json docs as the authoritative list for ignore rules in the cli docs.
The v10 branch is where new changelog entries for npm@10 get added ref: https://github.com/npm/cli/tree/release/v10
cafile is the correct config key Closes: npm/documentation#1337
BREAKING CHANGE: `npm init` now has a `type` prompt, and sorts the entries the created packages differently
Fixed code to deal w/ new esm export
BREAKING CHANGE: Upon publishing, in order to apply a default "latest" dist tag, the command now retrieves all prior versions of the package. It will require that the version you're trying to publish is above the latest semver version in the registry, not including pre-release tags. Implements [npm RFC7](https://github.com/npm/rfcs/blob/main/accepted/0007-publish-without-tag.md). Related to prerelease dist-tag: #7910 A part of npm 11 roadmap: npm/statusboard#898 --------- Co-authored-by: Jordan Harband <ljharb@gmail.com>
Removed npm 8 design change pending section note section from the documentation for `npm ls` https://docs.npmjs.com/cli/v10/commands/npm-ls?v=true#note-design-changes-pending Closes npm/documentation#1365, #6773
unnecessary files in node_modules
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: ![output of "npm search gar promisify" showing the name being duplicated](https://github.com/user-attachments/assets/2f34ece7-7563-4db1-a540-3bb661a4c3e0) After: ![output of "node . search gar promisify" showing the name being displayed correctly](https://github.com/user-attachments/assets/ba31fcd9-caf3-4a08-8bbb-7f5242f0098b)
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>
See Commits and Changes for more details.
Created by pull[bot]. Want to support this open source service? Please star it : )