chore: add job to notify on new release - #674
kangmingtay wants to merge 2 commits into
Conversation
Signed-off-by: Kang Ming <kang.ming1996@gmail.com>
7eadb09 to
f5ead6c
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Verolop
left a comment
There was a problem hiding this comment.
Looks good!
Before merging: moving the image copying into the private builder makes sense. I’d prefer to keep private-repo credentials there too and use polling, with a way to catch missed versions.
🔬 Go Test Coverage ReportSummary
Status✅ PASS DetailShow New Coverage |
| dist/install*.yaml | ||
|
|
||
| notify-builder: | ||
| needs: update-current-release |
There was a problem hiding this comment.
The release is published before the copy finishes. Dispatch can succeed even if the copy or digest check later fails, leaving a green upstream workflow and a release that isn’t ready in ECR. Someone updating the deployment pin could hit an image pull error or deploy an image that failed verification.
See our nightly build and compatibility workflow before reporting success or proposing new image pins. Can we also require the ECR copy and digest check to pass for that SHA before updating the deployment pin? 🙏
Uh oh!
There was an error while loading. Please reload this page.