Closed renovate[bot] closed 1 year ago
ghost
commented
1 year ago 
Sboonny
commented
1 year ago @ojeytonwilliams, the app is running without issue, but docker isn't running. Reading the notes, it didn't fail in their tests, do you have a guess of what is going on? https://github.com/npm/cli/wiki/Integrating-with-node
ojeytonwilliams
commented
1 year ago @Sboonny which problems did you run into? It all seems fine now.
Sboonny
commented
1 year ago The commit before this one had a version, that didn't work with docker and cypress didn't run, renovate got the one after it and it works now 👍
ojeytonwilliams
commented
1 year ago Bizarre. I wish it was possible to see the logs when that happens, but I was too late.
Sboonny
commented
1 year ago it was something about sha.key not valid
ojeytonwilliams
commented
1 year ago Since it's magically resolved itself I'm not too worried. Thanks, though.
This PR contains the following updates:
18.13.0->18.14.018.13.0->18.14.018.13->18.14Release 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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.