Skip to content

chore(deps): update dependency semantic-release-github to v5#6

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/semantic-release-github-5.x
Open

chore(deps): update dependency semantic-release-github to v5#6
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/semantic-release-github-5.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 16, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release-github ^4.0.17 -> ^5.0.0 age adoption passing confidence

Release Notes

hyper-expanse/open-source/semantic-release-github

v5.0.1

Compare Source

v5.0.0

Compare Source


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 is behind base branch, 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 added the refactor A modification to a project's repository that will not change the behavior for downstream consumers. label Mar 16, 2019
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 4 times, most recently from 5a3e3af to 75b5124 Compare March 19, 2019 15:59
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 8 times, most recently from 317a3f0 to 86b5bb6 Compare April 1, 2019 01:34
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 6 times, most recently from 4b05ec6 to 532ec1d Compare April 8, 2019 02:46
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 5 times, most recently from 380e438 to 7b5191a Compare April 16, 2019 14:56
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 5 times, most recently from b721090 to 95c73a4 Compare April 26, 2019 01:44
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch from 95c73a4 to b635626 Compare April 29, 2019 01:44
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 5 times, most recently from 47d0253 to 085b49a Compare May 11, 2019 03:27
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 3 times, most recently from 9f1dabe to 833bd39 Compare May 24, 2019 00:38
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 4 times, most recently from 4b86176 to 24e3b69 Compare June 5, 2019 02:39
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 8 times, most recently from 2e6e5af to 0df654b Compare June 13, 2019 02:33
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 2 times, most recently from 3529f0a to 9227f5d Compare June 19, 2019 04:52
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 2 times, most recently from 8469af7 to 300678b Compare July 5, 2019 00:34
@renovate renovate bot force-pushed the renovate/semantic-release-github-5.x branch 4 times, most recently from edeba37 to a5d5b04 Compare July 10, 2019 07:38
Signed-off-by: Renovate Bot <bot@renovateapp.com>
@renovate
Copy link
Copy Markdown
Contributor 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor A modification to a project's repository that will not change the behavior for downstream consumers.

Development

Successfully merging this pull request may close these issues.

1 participant