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

Use consistent parserOpts for commit-analyzer and release-notes-generator #143

Merged
merged 2 commits into from
Sep 7, 2023

Conversation

OmarJaroudi
Copy link
Contributor

@OmarJaroudi OmarJaroudi commented Aug 18, 2023

As per slack findings, we are passing these options to the release-notes-generator, but not to the commit-analyzer, which is why when using BREAKING or BREAKING CHANGES, you would see correct release notes but the version still ended up as a minor

After discussing this with @tagoro9 offline, we agreed to let both the commit-analyzer and the release-notes-generator use the default parserOpts

@OmarJaroudi OmarJaroudi marked this pull request as ready for review August 23, 2023 00:00
@OmarJaroudi OmarJaroudi requested a review from a team as a code owner August 23, 2023 00:00
@OmarJaroudi
Copy link
Contributor Author

OmarJaroudi commented Aug 23, 2023

Any idea if we can back-port this as a patch to v1? Or will it just have to ship in v3

@OmarJaroudi OmarJaroudi changed the title fix: pass parserOpts to commit-analyzer Use consistent parserOpts for commit-analyzer and release-notes-generator Aug 23, 2023
Copy link
Contributor

@Toolo Toolo left a comment

Choose a reason for hiding this comment

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

I think backporting this would be ideal. We'd need to branch off the latest 1.x, 2.x releases and add them to the semantic release config for it to work: https://semantic-release.gitbook.io/semantic-release/usage/workflow-configuration#maintenance-branches

Would you like to try it out? 😄

PS: there's a snapshot test failing

Copy link
Contributor

@tagoro9 tagoro9 left a comment

Choose a reason for hiding this comment

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

I think we would also need to have a maintenance branch so this gets fixed in the v1

@OmarJaroudi
Copy link
Contributor Author

now that we have a new semantic-release action we might not have to backport this after all 😄

@github-actions
Copy link

github-actions bot commented Sep 6, 2023

Release notes preview

Below is a preview of the release notes if your PR gets merged.


4.0.3 (2023-09-06)

Bug Fixes

  • remove custom parserOpts passed to release-notes-generator (8e8fd34)

Tests

  • update breaking snapshot (90739fa)

@OmarJaroudi OmarJaroudi merged commit e2c5c0c into main Sep 7, 2023
3 checks passed
@OmarJaroudi OmarJaroudi deleted the b/try_fixing_config branch September 7, 2023 22:54
@open-turo-bot
Copy link
Contributor

🎉 This PR is included in version 4.0.3 🎉

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.

4 participants