changeset-bot[bot]
commented
1 year ago ⚠️ No Changeset found
Latest commit: 4d7f60280797c02e14a46abbe84c0050f2d6f149
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver typesClick here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
github-actions[bot]
This PR contains the following updates:
16->18Release Notes
nodejs/node
### [`v18.14.0`](https://togithub.com/nodejs/node/releases/tag/v18.14.0): 2023-02-02, Version 18.14.0 'Hydrogen' (LTS), @BethGriggs prepared by @juanarbol [Compare Source](https://togithub.com/nodejs/node/compare/v18.13.0...v18.14.0) ##### Notable changes ##### Updated npm to 9.3.1 Based on the [list of guidelines we've established on integrating `npm` and `node`](https://togithub.com/npm/cli/wiki/Integrating-with-node), here is a grouped list of the breaking changes with the reasoning as to why they fit within the guidelines linked above. Note that all the breaking changes were made in [9.0.0](https://togithub.com/npm/cli/releases/tag/v9.0.0). All subsequent minor and patch releases after `npm@9.0.0` do not contain any breaking changes. ##### Engines > Explanation: the node engines supported by `npm@9` make it safe to allow `npm@9` as the default in any LTS version of `14` or `16`, as well as anything later than or including `18.0.0` - `npm` is now compatible with the following semver range for node: `^14.17.0 || ^16.13.0 || >=18.0.0` ##### Filesystem > Explanation: when run as root previous versions of npm attempted to manage file ownership automatically on the user's behalf. this behavior was problematic in many cases and has been removed in favor of allowing users to manage their own filesystem permissions - `npm` will no longer attempt to modify ownership of files it creates. ##### Auth > Explanation: any errors thrown from users having unsupported auth configurations will show `npm config fix` in the remediation instructions, which will allow the user to automatically have their auth config fixed. - The presence of auth related settings that are not scoped to a specific registry found in a config file is no longer supported and will throw errors. ##### Login > Explanation: the default `auth-type` has changed and users can opt back into the old behavior with `npm config set auth-type=legacy`. `login` and `adduser` have also been seperated making each command more closely match it's name instead of being aliases for each other. - Legacy auth types `sso`, `saml` & `legacy` have been consolidated into `"legacy"`. - `auth-type` defaults to `"web"` - `login` and `adduser` are now separate commands that send different data to the registry. - `auth-type` config values `web` and `legacy` only try their respective methods, npm no longer tries them all and waits to see which one doesn't fail. ##### Tarball Packing > Explanation: previously using multiple ignore/allow lists when packing was an undefined behavior, and now the order of operations is strictly defined when packing a tarball making it easier to follow and should only affect users relying on the previously undefined behavior. - `npm pack` now follows a strict order of operations when applying ignore rules. If a `files` array is present in the `package.json`, then rules in `.gitignore` and `.npmignore` files from the root will be ignored. ##### Display/Debug/Timing Info > Explanation: these changes center around the display of information to the terminal including timing and debug log info. We do not anticipate these changes breaking any existing workflows. - Links generated from git urls will now use `HEAD` instead of `master` as the default ref. - `timing` has been removed as a value for `--loglevel`. - `--timing` will show timing information regardless of `--loglevel`, except when `--silent`. - When run with the `--timing` flag, `npm` now writes timing data to a file alongside the debug log data, respecting the `logs-dir` option and falling back to `Configuration
📅 Schedule: Branch creation - "after 11pm every weekday,before 6am every weekday" in timezone Europe/Warsaw, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.