Skip to content
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.

Sign up for GitHub

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

Jump to bottom

npm v11 Roadmap #898

Open
13 of 23 tasks
wraithgar opened this issue Sep 25, 2024 · 4 comments
Open
13 of 23 tasks

npm v11 Roadmap #898

wraithgar opened this issue Sep 25, 2024 · 4 comments
Assignees
@wraithgar @reggi

Comments

@wraithgar
Copy link
Member

wraithgar commented Sep 25, 2024 •
edited
Loading

Initiative

npm 11

Before release
Beta Give feedback
  1. Align npm packages to npm 10's node engine range cli#7754
    Epic
    hashtagchris reggi
  2. [epic] devEngines #861
    7 of 7
    epic
    reggi wraithgar

For Release (breaking changes)
Beta Give feedback
  1. npm 11 engines declaration #899
  2. remove npm hooks code #901
  3. Remove npm audit fallback request #900
  4. fix: stop ignoring NODE_TLS_REJECT_UNAUTHORIZED when strictSSL is not defined make-fetch-happen#316
  5. fix(view): sort and truncate dist-tags cli#7808
  8. feat: adds type init-package-json#313
  10. feat: add bun.lockb to ignorelist npm-packlist#168

Post-release
Beta Give feedback
  2. npm 11 deps updates #913
    0 of 6
@ljharb

This comment has been minimized.

Sign in to view
@wraithgar

This comment has been minimized.

Sign in to view
@ljharb

This comment has been minimized.

Sign in to view
@wraithgar

This comment has been minimized.

Sign in to view
@wraithgar wraithgar mentioned this issue Sep 25, 2024
Open
1 task
@wraithgar wraithgar mentioned this issue Oct 11, 2024
Open
This was referenced Oct 14, 2024
Merged
Merged
Merged
Merged
This was referenced Nov 14, 2024
Merged
Merged
Merged
@reggi reggi mentioned this issue Nov 22, 2024
Merged
wraithgar pushed a commit to npm/cli that referenced this issue Nov 25, 2024
@reggi
fix!: publishing prerelease requires explicit tag (#7910)
16b7367 
BREAKING CHANGE: When publishing a package with a pre-release version,
you must explicitly specify a tag.
 
ref: npm/statusboard#898
@reggi reggi mentioned this issue Nov 26, 2024
Merged
@reggi reggi mentioned this issue Dec 5, 2024
Open
wraithgar pushed a commit to npm/cli that referenced this issue Dec 6, 2024
@reggi @ljharb
feat!: no implicit latest tag on publish when latest > version (#7939)
f3ac7b7 
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wraithgar wraithgar

@reggi reggi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wraithgar @ljharb @reggi