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

fix(deps): update dependency @semantic-release/error to v3 #167

Merged
merged 1 commit into from
Oct 30, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/error ^2.1.0 -> ^3.0.0 age adoption passing confidence

Release Notes

semantic-release/error

v3.0.0

Compare Source

BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

Configuration

📅 Schedule: 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, click this checkbox.

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

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 47437af to 0e26cba Compare September 17, 2021 20:52
@renovate renovate bot changed the title fix(deps): update dependency @semantic-release/error to v3 fix(deps): update semantic-release monorepo (major) Sep 17, 2021
Copy link
Member

@travi travi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these changes raise the minimum engines requirement, which is a breaking change for this package. we need to update the defined engines here in order to pull in these changes. lets add ls-engines to CI to alert us about this in the future

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ae65f28 to e89647f Compare September 20, 2021 03:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e89647f to 35e3e89 Compare September 22, 2021 00:18
@renovate renovate bot changed the title fix(deps): update semantic-release monorepo (major) fix(deps): update dependency @semantic-release/error to v3 Sep 22, 2021
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 35e3e89 to 049f17f Compare September 27, 2021 04:21
@jdbruijn
Copy link

This PR should now be compatible with this version as it has gotten the same version requirement in #170. Only thing is the added ls-engines which I think also need the <17 in the engines based on the error, but I have no experience with the tool so not sure.

@travi
Copy link
Member

travi commented Sep 27, 2021

there is a bug in ls-engines that is preventing it from evaluating the engines requirements of our tree correctly in the situation (our definition exactly matches the requirements of the tree) that happens once error would be updated. once that bug is updated, we'll be able to get this updated. in the meantime, there should be no behavioral difference.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 68b89f0 to 572ee56 Compare October 11, 2021 03:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 572ee56 to 8810165 Compare October 25, 2021 04:58
@travi travi merged commit ef37296 into master Oct 30, 2021
@travi travi deleted the renovate/major-semantic-release-monorepo branch October 30, 2021 05:32
@github-actions
Copy link

🎉 This PR is included in version 6.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants