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

Merged
merged 1 commit into from
Aug 22, 2019

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 22, 2019

This PR contains the following updates:

Package Type Update Change
@semantic-release/github devDependencies patch 5.4.2 -> 5.4.3
@semantic-release/npm devDependencies patch 5.1.13 -> 5.1.15

Release Notes

semantic-release/github

v5.4.3

Compare Source

Bug Fixes
semantic-release/npm

v5.1.15

Compare Source

Bug Fixes

v5.1.14

Compare Source

Bug Fixes
  • package: update execa to version 2.0.2 (2a45e25)

Renovate configuration

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

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

👻 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 Renovate Bot. View repository job log here.

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 80969ba to 9e78bcc Compare August 22, 2019 19:46
@renovate renovate bot changed the title chore(deps): update dependency @semantic-release/github to v5.4.3 chore(deps): update semantic-release monorepo Aug 22, 2019
@renovate renovate bot merged commit a7d20c5 into master Aug 22, 2019
@renovate renovate bot deleted the renovate/semantic-release-monorepo branch August 22, 2019 20:42
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.

None yet

1 participant