-
Notifications
You must be signed in to change notification settings - Fork 324
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
Change in artifact name - Gren no longer creates release notes! #162
Comments
Hello @tomshercliff, It might be a problem related to #134. Could you tell me the names of the tags that |
Hi @alexcanessa - the names of the tags which are picked up are below: Then we changed the artifactId in the pom from chronicle-fix-parent to chronicle-fix, and the tags below were not picked up: So are you suggesting that (relating to #134) because chronicle-fix-1.5.18 will be sorted alphabetically before chronicle-fix-parent-1.5.17, this is causing Gren to still view chronicle-fix-parent-1.5.16 and chronicle-fix-parent-1.5.17 as the 2 latest ones and hence only generate notes for 1.5.17? |
@tomshercliff yep something like that. A release is going to get out soon and should fix this. |
@alexcanessa thanks |
Hi @alexcanessa - has this issue been fixed? Thanks! |
It should be fixed by 0.16.0. Could you check if you still have a problem? //cc @tomshercliff @RobAustin |
Hi @alexcanessa - seems like we still have an issue here. It still seems to be trying to access the latest release when the release names are sorted alphabetically: [09:25:27][Step 2/2] Running command: [/usr/bin/gren, release] in /home/teamcity/agent_chronicle3/agent/3/work/84985a4243a311c4/ReleaseAutomation/projects/Chronicle-FIX Any thoughts on this? |
This should be fixed by 2460fac |
We have recently changed the artifact name in the pom of one of our projects, and since then Gren doesn't seem to find new released versions to generate release notes when running 'gren release' (it only finds the previous two versions before the name change occurred - which have already had release notes generated!).
The tag created by maven release:prepare is visible in Github, and release notes can be added manually which I assume would make them into a Release as far as Github is concerned?
Incidentally, running 'gren release —tags=all' did generate notes for all versions, including the new ones since the name change.
How does gren identify the last two releases in github to generate the last two release notes?
Thanks!
The text was updated successfully, but these errors were encountered: