Repository navigation
ci(release): wait ten minutes for a new version to appear on Open VSX - #3
Merged
Merged
Conversation
Problem - Open VSX reported a successful publish, but the new version took longer than the two and a half minutes the confirm step waited. The run went red for a release that was live. Solution - Wait up to ten minutes, and keep the log quiet while the version is not yet listed.
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
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.
The first OIDC releases published successfully, but two runs failed at the confirm step because Open VSX listed the version after the old 2.5-minute wait. The wait is now ten minutes. The file stays identical across the extension repositories.