Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 8, 2021

Mend Renovate

This PR contains the following updates:

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

Release Notes

semantic-release/git

v9.0.1

Compare Source

Bug Fixes
semantic-release/github

v7.2.3

Compare Source

Bug Fixes

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
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

v17.4.5

Compare Source

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

v17.4.4

Compare Source

Bug Fixes

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

v17.4.1

Compare Source

Bug Fixes

v17.4.0

Compare Source

Features

v17.3.9

Compare Source

Bug Fixes

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
Copy link

commit-lint bot commented Feb 8, 2021

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
Copy link
Author

renovate bot commented Feb 8, 2021

⚠️ 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/[email protected]
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 [email protected]
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 renovate bot force-pushed the renovate/semantic-release-monorepo branch 11 times, most recently from e7c4805 to 96a364b Compare February 13, 2021 00:10
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.3.8 chore(deps): update dependency semantic-release to v17.3.9 Feb 13, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from a77258b to 329508c Compare February 19, 2021 19:28
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from 5dcba1e to 8adebc8 Compare February 26, 2021 04:39
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.3.9 chore(deps): update dependency semantic-release to v17.4.0 Feb 26, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 6 times, most recently from 1aa2e7a to 56a7db9 Compare March 2, 2021 13:50
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from bb67501 to 13a1fe0 Compare November 5, 2021 16:12
@renovate
Copy link
Author

renovate bot commented Nov 5, 2021

⚠ 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: [email protected]
npm ERR! Found: @semantic-release/[email protected]
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 [email protected]
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/[email protected]
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   peer @semantic-release/changelog@"^3.0.0" from [email protected]
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 renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from be205c1 to 0251e72 Compare November 11, 2021 12:14
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from c06eff0 to 10f870b Compare November 21, 2021 13:20
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from 92343f0 to 36abdec Compare November 29, 2021 19:03
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from 581e698 to 1d22c23 Compare December 6, 2021 18:19
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 1d22c23 to ecd7bb4 Compare December 7, 2021 16:16
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from ecd7bb4 to 6d45798 Compare December 8, 2021 18:52
@renovate
Copy link
Author

renovate bot commented Mar 25, 2023

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.

Copy link
Author

renovate bot commented Dec 8, 2024

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.

@renovate renovate bot changed the title chore(deps): update semantic-release monorepo chore(deps): update semantic-release monorepo - abandoned Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant