hubcio opened a new pull request, #3259: URL: https://github.com/apache/iggy/pull/3259
Post-merge auto-publish runs on every push to master, but component versions only change when a human bumps them. So the same immutable git tag (e.g. server-0.8.1-edge.1) is re-seen on every run after the one that first created it. check-tags treated a pre-existing tag pointing at a different commit as a wrong-target hard failure and exited 1, turning the whole workflow red and cascade-skipping publish-rust-crates and build-python-wheels. Treat tag existence as a routing signal, not a failure. In auto-publish mode (create_edge_docker_tag=true) an existing tag means the version is already released: check-tags reports it informationally instead of failing, and docker-manifests sets should_tag=false so the versioned git tag and :version manifest are skipped. The rolling :edge Docker image is still refreshed every run, and the per-component versioned release runs exactly once - on the run after a version bump, when the tag is missing. The manual publish path is unchanged: a wrong-target tag there is still a fast hard failure, because a stable release tag pointing at the wrong commit is a real error rather than the expected steady state. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
