-
Notifications
You must be signed in to change notification settings - Fork 22
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
chore: fixup release action versioning and notes process #1124
chore: fixup release action versioning and notes process #1124
Conversation
…ng a separate branch
ac49421
to
853c57b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're planning to get rid of the individual makefiles sooner or later, right?
Otherwise it might be worth thinking of using include ... ?
853c57b
to
3813f0a
Compare
@hilmarf Currently unplanned, but we can create an issue for this so I can take care of it. I would really like to just get the releases working right now. |
otherwise the components in the CTF will still be flagged as dev if used from the release flow
3813f0a
to
00f33d5
Compare
What this PR does / why we need it
Makes sure that release notes are correctly drawn in and that we always have the version set correctly in our CTFs.
Which issue(s) this PR fixes
This fixes up the release action in 2 important ways:
VERSION
variable whileEFFECTIVE_VERSION
is a combination of VERSION+COMMIT by default. I didnt want to change this behavior originally, so now I started to use VERSION for the Makefiles (which also means I had to export them as settable). This now leads to correct CTF versionsv0.19.0-rc.1
instead ofv0.19.0-dev
for example.As such its a follow up from #1120 and #1077