Conversation
Signed-off-by: Tom Hayward <thayward@infoblox.com>
|
This looks like the current "process" but honestly we should probably (if we're gonna switch). Just use github chart-releaser action. https://github.com/helm/chart-releaser |
Looks like this action does not allow configuring the package-path to |
| # Update Changelog | ||
| date_str=$(date +%Y-%m-%d) | ||
| # Use perl for consistent behavior across platforms (macOS/Linux) regarding newlines in replacement | ||
| perl -i -pe "s/^## master \/ unreleased/## master \/ unreleased\n\n## $new_version \/ $date_str/" CHANGELOG.md |
There was a problem hiding this comment.
Is that installed in the job container?
nschad
left a comment
nschad
left a comment
There was a problem hiding this comment.
Looks ok.
I don't know to be honest. anyway we can test this?
It needs to be on the default branch before we can test it. Once it's there, we should be able to trigger versions of it on any branch, meaning if the first PR has a bug, we can test that the follow-up PR fixes it. Should take two PRs max to get working. 🤞 |
Signed-off-by: Tom Hayward <thayward@infoblox.com> Signed-off-by: chorst <chorst@infoblox.com>
2 participants
What this PR does:
Automates the release workflow. It is manually triggered (for now) from Actions tab. There is a helper
make bump-versionthat will look at the new entries in the changelog and apply semver rules to bump the version in Chart.yaml and CHANGELOG.md. Next it packages the chart, updates the index, and opens a PR with the changes.Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX],[DEPENDENCY]