Remove bitrotted patch image #674
Merged
Conversation
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
rtwalker
approved these changes
Jan 4, 2023
WireBaron
approved these changes
Jan 4, 2023
|
bors r+ |
bors bot
added a commit
that referenced
this pull request
Jan 4, 2023
674: Remove bitrotted patch image r=Smittyvb a=Smittyvb The `patch` Docker image hasn't been successfully built for 8 months, and the job to build it always fails due to an authentication error. Even if it got past that issue, it would still fail since it's still using pgx 0.2. This PR removes the image and the CI job that builds it. (originally noted at #664 (comment)) Co-authored-by: Smitty <[email protected]>
|
Build succeeded:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The
patchDocker image hasn't been successfully built for 8 months, and the job to build it always fails due to an authentication error. Even if it got past that issue, it would still fail since it's still using pgx 0.2.This PR removes the image and the CI job that builds it.
(originally noted at #664 (comment))