chore(deps): update semantic-release monorepo - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/git	9.0.0 -> 9.0.1
@semantic-release/github	7.2.0 -> 7.2.3
@semantic-release/npm	7.0.10 -> 7.1.3
semantic-release	17.3.7 -> 17.4.7

---

Release Notes

semantic-release/git

v9.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v5 (#​228) (f536d60)

semantic-release/github

v7.2.3

Compare Source

Bug Fixes

• improve text in comment (#​367) (0aa2ba1)

v7.2.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v10 (1a28625)

v7.2.1

Compare Source

Bug Fixes

• allow proxy to be false and fallback an empty string (#​356) (bea917f)

semantic-release/npm

v7.1.3

Compare Source

Bug Fixes

• use NPM_CONFIG_USERCONFIG in get-registry to match auth (#​362) (13200ca)

v7.1.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v10 (80fde1e)

v7.1.1

Compare Source

Bug Fixes

• deps: update dependency normalize-url to v6 (97ca719)

v7.1.0

Compare Source

Features

• use npm v7 (#​304) (a15c017)

semantic-release/semantic-release

v17.4.7

Compare Source

Bug Fixes

• engines: fixed defined node version to account for the higher requirement from the npm plugin (#​2088) (ea52e17)

v17.4.6

Compare Source

Bug Fixes

• marked: reverted upgrade to v3 (#​2087) (5edff69)

v17.4.5

Compare Source

Bug Fixes

• deps: update dependency marked to v3 (6e4beb8)

v17.4.4

Compare Source

Bug Fixes

• corrected spelling of invalid plugin config error (#​1979) (80e1665)

v17.4.3

Compare Source

Bug Fixes

• bump minimal version of lodash to address CVE-2021-23337 (#​1931) (55194c1)

v17.4.2

Compare Source

Bug Fixes

• deps: update dependency hosted-git-info to v4 (#​1838) (44b3344)

v17.4.1

Compare Source

Bug Fixes

• deps: peer dependecy error with marked-terminal (#​1829) (07f12b9)

v17.4.0

Compare Source

Features

• config: Use cosmiconfig defaults to support .cjs config files (#​1815) (3ecc196), closes #​1814

v17.3.9

Compare Source

Bug Fixes

• update link to GitLab CI introduction (#​1794) (a9be97b)

v17.3.8

Compare Source

Bug Fixes

• deps: update dependency marked to v2 (a2eaed0)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

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

[commit-lint]

Chore

• deps: update semantic-release monorepo (6d45798)

Contributors

renovate-bot

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

• @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
• @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
• @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
• @Commit-Lint merge disable will desactivate merge dependabot PR
• @Commit-Lint review will approve dependabot PR
• @Commit-Lint stop review will stop approve dependabot PR

[renovate]

⚠️ 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 check 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: @semantic-release/changelog@5.0.1
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"5.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @semantic-release/changelog@"^3.0.0" from npm-github-config@2.0.1
npm ERR! node_modules/npm-github-config
npm ERR!   dev npm-github-config@"2.0.1" 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/2021-05-06T14_49_47_941Z-debug.log

[renovate]

⚠️ 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 check 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: @semantic-release/changelog@5.0.1
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"5.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @semantic-release/changelog@"^3.0.0" from npm-github-config@2.0.1
npm ERR! node_modules/npm-github-config
npm ERR!   dev npm-github-config@"2.0.1" 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/2021-06-01T17_47_16_988Z-debug.log

[renovate]

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: npm-github-config@2.0.1
npm ERR! Found: @semantic-release/changelog@5.0.1
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"5.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @semantic-release/changelog@"^3.0.0" from npm-github-config@2.0.1
npm ERR! node_modules/npm-github-config
npm ERR!   dev npm-github-config@"2.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @semantic-release/changelog@3.0.6
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   peer @semantic-release/changelog@"^3.0.0" from npm-github-config@2.0.1
npm ERR!   node_modules/npm-github-config
npm ERR!     dev npm-github-config@"2.0.1" 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/2021-12-08T18_52_43_349Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.