-
Notifications
You must be signed in to change notification settings - Fork 20
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
Not excluding labels with branch-diff v2.0.0 #45
Labels
Comments
Eyeballing #43 I think [email protected] is no longer fetching labels for commits before attempting to filter in Lines 75 to 81 in a28abae
collectCommitLabels() : Lines 105 to 116 in 603d3d0
Later on Line 158 in a28abae
calls processCommits() in changelog-maker which does fetch labels but it doesn't do any filtering.
|
Merged
This was referenced Apr 14, 2022
🎉 This issue has been resolved in version 2.0.4 🎉 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
In today's release session, we started preparing the next Node.js 17 and spotted that the same
branch-diff
command produced different results for v2.0.0 and v1.10.5. Generally, it looked like there were some commits included in the list that should have been excluded based on the labels provided.This is the command I used:
npx [email protected] upstream/v17.x-staging upstream/master --exclude-label=semver-major,dont-land-on-v17.x,backport-requested-v17.x,backport-blocked-v17.x,backport-open-v17.x,backported-to-v17.x --filter-release
Specifically for this command, I spotted that semver majors are appearing in the output for v2.0.0 but not v1.10.5.
Output
I can try and find a smaller recreate but it's evening here and I didn't want to forget to raise this issue 😅.
The text was updated successfully, but these errors were encountered: