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 conventional-commits-parser to v5 #514

Merged
merged 1 commit into from
Aug 28, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 28, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
conventional-commits-parser (source) ^4.0.0 -> ^5.0.0 age adoption passing confidence

Release Notes

conventional-changelog/conventional-changelog (conventional-commits-parser)

v5.0.0: conventional-changelog-conventionalcommits: v5.0.0

Compare Source

⚠ BREAKING CHANGES
  • always use H2 heading for versions (#​920)
Bug Fixes

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.

@gr2m gr2m merged commit a7201b6 into master Aug 28, 2023
21 checks passed
@gr2m gr2m deleted the renovate/conventional-commits-parser-5.x branch August 28, 2023 20:29
@github-actions
Copy link

🎉 This PR is included in version 10.0.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@lukehsiao
Copy link

We're noticing some issues with our semantic-release setup today.

I noticed this was reverted: ab3ee9f

And now unreverted, with seemingly no other change.

What's different this time?

@travi
Copy link
Member

travi commented Aug 28, 2023

I noticed this was reverted: ab3ee9f

sorry for the extra confusion, that revert was accidental. we had some dev dependencies related to the conventional-commits project get auto merged last night despite failing ci builds, so the accidental merges needed to be reverted and fixes needed to be applied to our pipeline to prevent such merges. i accidentally included that package in the list that i reverted because of the similar naming.

@lukehsiao
Copy link

Makes sense, thanks!

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