-
Notifications
You must be signed in to change notification settings - Fork 74
Closed
Description
Goal(s):
- Standardize reasonable defaults
Timeline:
- Generally Available: October 2022
- End-of-Life: October 2023
Phased Roll-Out Plan:
- Wednesday Oct. 19th
- Release
[email protected]& set dist-tags tonext-9(which is already being used for our pre-releases/rcs) - Post Changlog with release notes & reference to phased GA timeline
- Continue cutting minors/patches to address any feedback or unexpected issues arising from the outlined changes
- Release
- Wednesday Nov. 9th (~3 weeks from initial release)
- Exit criteria to ensure
[email protected]is considered "non-breaking" should be codified (collaboration betweennpm& the Release WG) - Set dist-tags for
latestfor[email protected] - PR is open to land
[email protected]innodejs/node'smainbranch
- Exit criteria to ensure
- Wednesday Dec. 7th (~4 weeks after GA)
- PR is open to backport
[email protected]innode@19
- PR is open to backport
- Wednesday Jan. 18th (~6 weeks after v19 backport)
- PR is open to backport
[email protected]innode@18
- PR is open to backport
Breaking Changes:
Removals:
- BREAKING CHANGE(config): remove dangerous auth configs #485
- BREAKING CHANGE(config): Remove
sso-type#452 - BREAKING CHANGE(config): Remove all options but
legacyandwebauthnfromauth-type#453 - BREAKING CHANGE(config): Remove
loglevel=timing#454 - BREAKING CHANGE(shrinkwrap): Remove
shrinkwrap.jsonas an unignorable file #459 - BREAKING CHANGE(explain): Remove path support #447
- BREAKING CHANGE(set-script): Remove command #449
- BREAKING CHANGE(birthday): Remove command #450
- BREAKING CHANGE(adduser): Remove alias for
npm login#451 - BREAKING CHANGE(bin): remove command #537
- BREAKING CHANGE(fs): stop changing folder permissions #540
Changes:
- BREAKING CHANGE(bin): command should not return non-existent paths #479
- BREAKING CHANGE(engines): engines support for npm
9.0.0#519 - BREAKING CHANGE(config): Differentiate
--timingfrom--loglevel#455 - BREAKING CHANGE(config): map legacy options to
--location&--strategy#458 - BREAKING CHANGE(lockfile): migrate to
v3#446 - BREAKING CHANGE(spec): Normalize
x,x@&x@*#460 - BREAKING CHANGE(logs): Write process specific timing file instead of newline delimited json in
*_timing.json#456 - BREAKING CHANGE(access): remove old commands #486
- BREAKING CHANGE(bin): remove command #537
- BREAKING CHANGE(install): default to
--install-links=true#510 - BREAKING CHANGE(publish):
--accessdefaults to"public"for all packages #508 - BREAKING CHANGE(git): default to
HEADgit ref instead ofmaster#503 - BREAKING CHANGE(login): change default
--auth-type#544 - feat(display): standardize
stderr&stdout#546 - BREAKING CHANGE(config): npm 9 should refuse to set deprecated config items. #535
- BREAKING CHANGE(config):
--npm-version&--node-versionshould be removed #575
Dependencies Requiring Major Updates:
npm-packlist- feat!: major refactor npm-packlist#88- BREAKINGCHANGE(packlist): consistently resolve globbing patterns (ref. [BUG] npm publish ignores files exclusion glob cli#2441)
hosted-git-info- BREAKING CHANGE: set default git ref toHEADhosted-git-info#142- BREAKINGCHANGE(repo): assumes
masterbranch (ref. [BUG] npm repo <pkg> assumes amasterbranch cli#4867)
- BREAKINGCHANGE(repo): assumes
@npmcli/template-oss- feat: make template-oss postinstall commit a breaking change for majors template-oss#180
Features:
- feat(update): support saving back to
package.json(potentially via--save) #457 - feat(access): add new
get,set&list#477