-
Notifications
You must be signed in to change notification settings - Fork 40
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
Only last commit made has effect on verison bump and written to changelog #16
Comments
Not sure about the issue here. The I have just updated the dependencies and added more debug output in v2.0.1 of this plugin. However, I'm surprised not to see debug output from this plugin at all in your output. Can you please update release-it and this plugin, and run this to see what's going on, in what order:
In your example repo I get this (after going back one commit), which seems correct:
|
@webpro I did an update of the repos dependencies. Also invited you as collaborator.
Git log
Debug
You can try doing multiple commits of different types and see that only last commit is written to changelog and influences version bump. |
I found a problem. When creating CI with Github Actions using
Thank you @webpro for an awesome tool! |
Thanks @b12k! Glad you figured it out. I've added a comment to the docs on both this plugin and release-it itself. |
@b12k Thanks, wouldn't have found that in a million years. |
Hello.
In my
release-it
+@release-it/conventional-changelog
setup only last commit made is affecting version bump and written to the changelog.Also only last commit is taken in to consideration when bumping a version.
So if:
feat
fix
<= this one usedExample repo: https://github.com/b12k/gh-action-release-it
This repo uses github action to do an automated release on PR merge to master (using rebase).
I would appreciate some advice on why it may happen.
Thanx in advance.
UPDATE:
Here is git log
Debug
The text was updated successfully, but these errors were encountered: