chore(deps): update dependency @semantic-release/npm to v9

renovate[bot] commented 2 years ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/npm	`8.0.3` -> `9.0.0`

Release Notes

semantic-release/npm

### [`v9.0.0`](https://togithub.com/semantic-release/npm/releases/v9.0.0) [Compare Source](https://togithub.com/semantic-release/npm/compare/v8.0.3...v9.0.0) ##### Bug Fixes - add `preferLocal` option to allow execa to use local npm version ([#445](https://togithub.com/semantic-release/npm/issues/445)) ([002439e](https://togithub.com/semantic-release/npm/commit/002439ef93ddef31170dbf0361ddc89d2b02eee8)) - updated the peer requirement for `semantic-release` to the new stable version ([575a5a4](https://togithub.com/semantic-release/npm/commit/575a5a402e61d7593c0b8a33c129b13ea2622086)) - updated the peer requirement on `semantic-release` to a version matching the engines definition of this package ([2d1f5f2](https://togithub.com/semantic-release/npm/commit/2d1f5f26c7f1f82c3249106ddb4b486dcc35997f)) - upgrade npm dependency to v8 ([a12d6e5](https://togithub.com/semantic-release/npm/commit/a12d6e59155a2fce7767bac9f54d649635acb5ad)) ##### BREAKING CHANGES - the minimum required peer of `semantic-release` has been raised to match the `engines.node` requirements of this package - npm v8 dropped support for node v15, so it is no longer supported in this plugin. this should be low impact since node v15 is already EOL Co-authored-by: Matt Travi

Configuration

📅 Schedule: 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.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate[bot] commented 2 years ago

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm notice 
npm notice New minor version of npm available! 8.1.2 -> 8.4.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.4.0>
npm notice Run `npm install -g npm@8.4.0` to update!
npm notice 
npm WARN using --force Recommended protections disabled.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @aurodesignsystem/auro-hyperlink@3.0.0
npm ERR! Found: semantic-release@18.0.1
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"18.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=19.0.0" from @semantic-release/npm@9.0.0
npm ERR! node_modules/@semantic-release/npm
npm ERR!   dev @semantic-release/npm@"9.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-01-28T17_50_59_945Z-debug-0.log

CLAassistant commented 2 years ago

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

renovate[bot] commented 2 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 9.x releases. However, if you upgrade to 9.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

AlaskaAirlines / auro-hyperlink