-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
🐛 Bug: BREAKING CHANGE:
not recognised
#507
Comments
Heh, #140 was never merged, and I never followed up on the detection it was meant to add. Would definitely accept a remake of it (or an equivalent addition)! |
ah - so I think the docs are wrong then. Shame. TBH right now I just want to ship a release. The |
Baffled as to why these tests are passing: https://github.com/JoshuaKGoldberg/should-semantic-release/blob/main/src/getCommitMeaning.test.ts Anyway, I think I need to hack my package.json to get past this for now |
Oh! #168 was merged later on. |
There https://github.com/johnnyreilly/azdo-npm-auth/actions/runs/12216118613/job/34078891515 - I feel a little dirty, but I shipped! |
I don't know why #168 doesn't appear to be working for me - but I've managed to work around the issue at least. |
Bug Report Checklist
main
branch of the repository.Expected
BREAKING CHANGE:
to be detected as a breaking change releaseActual
See https://github.com/johnnyreilly/azdo-npm-auth/actions/runs/12215799512/job/34078200073#step:5:11
Additional Info
johnnyreilly/azdo-npm-auth#20
It looks that
feat!:
is also not recognised - same log messages:johnnyreilly/azdo-npm-auth#21
https://github.com/johnnyreilly/azdo-npm-auth/actions/runs/12215949788/job/34078528733#step:5:11
Looking at #140 it suggests this ought to work. But it doesn't. Or I'm missing something
The text was updated successfully, but these errors were encountered: