fix(ci): make publish-s3 wait for generate-sha256sum#25265
Merged
Conversation
github-actions
Bot
added
the
domain: ci
thomasqueirozb
added
the
no-changelog
pront
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
publish-s3job uploads release artifacts topackages.timber.iobut does not currently depend ongenerate-sha256sum, which producesvector-<ver>-SHA256SUMS. As a result,publish-s3can finish before the checksum file is generated, so downstream consumers that expectSHA256SUMSunderpackages.timber.io/vector/<ver>/(e.g.install.shverification, post-release verification tooling) can race the workflow.Fix by adding
generate-sha256sumtopublish-s3'sneeds:list.publish-githubalready has this dependency.This is a small/rare race condition.
Vector configuration
NA
How did you test this PR?
NA
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
NA