Use nightly tag for legacy x86-64 builder images - #167
Merged
Conversation
ponylang-main
added
the
discuss during sync
shared-docker is switching the legacy LibreSSL 3.9.2 and OpenSSL 1.1.1w builder images to push nightly builds as "nightly" instead of "latest", aligning with the convention all the newer multi-arch builders already use.
SeanTAllen
force-pushed
the
update-legacy-image-tags
branch
from
September 5, 2026 01:56
4c784b5 to
0a383ce
Compare
ponylang-main
removed
the
discuss during sync
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.
ponylang/shared-docker#141 switches the legacy LibreSSL 3.9.2 and OpenSSL 1.1.1w builder images to push nightly builds as
nightlyinstead oflatest, aligning with the convention all the newer multi-arch builders already use.One reference in the breakage workflow (the lint job) already used
:nightly— this PR updates the remaining three:latestreferences so everything is consistent once the shared-docker change lands.