Repository navigation
github-builder: resolve source date epochs for reproducible builds - #1376
Merged
Merged
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
vvoland
approved these changes
Oct 19, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
relates to docker/github-builder#307
Add a shared source date epoch resolver for the build and bake workflow changes proposed in docker/github-builder#307. It accepts a Unix timestamp, including zero, or
committo use the event commit's committer time without a checkout. It returns the epoch and corresponding ISO timestamp so the workflows can use the same time for build outputs and generated image metadata.Keeping this logic in the toolkit avoids duplicating parsing, validation, and GitHub API calls across the workflows and provides focused unit coverage. The workflows will consume the helper after a runtime release. This supports reproducible image contents without promising identical final index digests, since provenance contains execution-specific data.