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.4 - abandoned #148

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 4, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 17.2.3 -> 17.4.4 age adoption passing confidence

Release Notes

semantic-release/semantic-release

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)

v17.3.7

Compare Source

Bug Fixes

v17.3.6

Compare Source

Bug Fixes

v17.3.5

Compare Source

Bug Fixes

v17.3.4

Compare Source

Bug Fixes

v17.3.3

Compare Source

Bug Fixes

v17.3.2

Compare Source

Bug Fixes

v17.3.1

Compare Source

Bug Fixes

v17.3.0

Compare Source

Features

v17.2.4

Compare Source

Bug Fixes

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Never, 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 WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested review from dezren39 and a team as code owners February 4, 2021 19:04
@renovate renovate bot added the dependencies label Feb 4, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from c9384c0 to fc82558 Compare February 8, 2021 17:56
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.3.7 chore(deps): update dependency semantic-release to v17.3.8 Feb 8, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from fc82558 to 2f1b616 Compare February 12, 2021 23:28
@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 12, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 2f1b616 to de25502 Compare February 26, 2021 04:38
@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 from de25502 to f38157e Compare March 3, 2021 20:41
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.0 chore(deps): update dependency semantic-release to v17.4.1 Mar 3, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from f38157e to 87c675b Compare March 11, 2021 21:51
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.1 chore(deps): update dependency semantic-release to v17.4.2 Mar 11, 2021
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 87c675b to 3553bf1 Compare March 30, 2021 10:24
@renovate
Copy link
Author

renovate bot commented Mar 30, 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: yarn.lock

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 3553bf1 to edb4dde Compare May 12, 2021 19:06
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.4.2 chore(deps): update dependency semantic-release to v17.4.3 May 12, 2021
renovate bot automated dependency management

| datasource | package          | from   | to     |
| ---------- | ---------------- | ------ | ------ |
| npm        | semantic-release | 17.2.3 | 17.4.4 |
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from edb4dde to 1d8dc61 Compare June 16, 2021 11:11
@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 Jun 16, 2021
@renovate
Copy link
Author

renovate bot commented Mar 23, 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.4 chore(deps): update dependency semantic-release to v17.4.4 - abandoned Jul 15, 2023
@renovate
Copy link
Author

renovate bot commented Jul 15, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants