-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix: Fix Release Automation Workflow #498
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Alfredo Gutierrez <[email protected]>
Signed-off-by: Alfredo Gutierrez <[email protected]>
@AlfredoG87 I took the liberty to push another commit to this branch. It replaces 'bumpVersion' with 'versionAsSpecified' that is already available (original motivated by how things are done in 'hedera-services'). 'versionAsSpecified' takes care of updating 'version.txt'. The Gradle configuration I added extends 'versionAsSpecified' to also update the 'Chart.yaml' files. See: |
This uses as much as possible of the functionality already provided through 'hiero-gradle-conventions' See: - https://github.com/hiero-ledger/hiero-gradle-conventions/tree/main?tab=readme-ov-file#publishing - https://github.com/hiero-ledger/hiero-gradle-conventions/blob/main/src/main/kotlin/org.hiero.gradle.feature.versioning.gradle.kts#L88-L102 Signed-off-by: Jendrik Johannes <[email protected]>
810dbd6
to
f03d7cc
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.
Review applies to .github/workflows/release-automation.yaml
Description:
The release automation workflow was broken due to PR for Build migration to Hiero gradle plugins, this fixes it the issue with the version not been passed along correctly to the gradle
bumpVersion
taskRelated issue(s):
Fixes #496
Notes for reviewer:
Checklist