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 dependency semantic-release to v17.4.7 - abandoned #151

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 12, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 17.4.2 -> 17.4.7 age adoption passing confidence

Release Notes

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)

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 816bc4e to 430c38c Compare July 2, 2021 20:33
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.3 chore(deps): update dependency semantic-release to v17.4.4 Jul 2, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 430c38c to 11a5381 Compare August 16, 2021 07:34
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.4 chore(deps): update dependency semantic-release to v17.4.5 Aug 16, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 11a5381 to 410118c Compare August 23, 2021 21:13
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.5 chore(deps): update dependency semantic-release to v17.4.6 Aug 23, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 410118c to b9b1be3 Compare August 25, 2021 19:58
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.6 chore(deps): update dependency semantic-release to v17.4.7 Aug 25, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from b9b1be3 to 8c69dec Compare October 9, 2021 11:32
@renovate
Copy link
Author

renovate bot commented Mar 24, 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.

@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.7 chore(deps): update dependency semantic-release to v17.4.7 - abandoned Jul 11, 2023
@renovate
Copy link
Author

renovate bot commented Jul 11, 2023

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.

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