We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem description (if applicable) We currently have no release automation to:
Proposed change Add similar release automation to that of airshipctl/krm functions: airshipit/airshipctl#354
I believe the current direction is to use a single version (git tag) for all images in this repo, rather than independent versions for each image.
The text was updated successfully, but these errors were encountered:
https://review.opendev.org/c/airship/images/+/784161
Sorry, something went wrong.
Add release automation for image tags
2a5218c
Relates-To: #13 Signed-off-by: Sean Eagan <seaneagan1@gmail.com> Change-Id: Iecfc6e4ddf456ec2bd5269829fbbf6ea9024ce83
@seaneagan can we close this one?
still need to do release notes automation
@seaneagan thanks. This was leftover from the other day before we had a chance to talk on Flight Plan. Understood.
I think the plan for now is to only version the directly user facing components (airshipctl, treasuremap), so closing this.
seaneagan
No branches or pull requests
Problem description (if applicable)
We currently have no release automation to:
Proposed change
Add similar release automation to that of airshipctl/krm functions: airshipit/airshipctl#354
I believe the current direction is to use a single version (git tag) for all images in this repo, rather than independent versions for each image.
The text was updated successfully, but these errors were encountered: