This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
chore: run docker rc release separately #3342
Merged
Conversation
This file contains 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
When we publish an rc to npm, sometimes the release isn't available by the time we try to publish an rc to docker hub. Change the docker publish to be a separate job to give it a bit of time before running so npm has a chance to propagate the rc but also so we can re-run if it's too fast.
This was referenced Nov 30, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When we publish an rc to npm, sometimes the release isn't available
by the time we try to publish an rc to docker hub.
Change the docker publish to be a separate job to give it a bit of
time before running so npm has a chance to propagate the rc but also
so we can re-run if it's too fast.