ci: publish pgvector images to GHCR - #1
Merged
Merged
Conversation
Co-Authored-By: Zero <zero@vm0.ai>
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.
Summary
linux/amd64andlinux/arm64pgvector images toghcr.io/vm0-ai/pgvectorpg17,pg17-bookworm,0.8.5-pg17, and0.8.5-pg17-bookwormmasterupdate or a manual workflow dispatchMakefileandDockerfiledivergeUser impact
This creates a vm0-owned GHCR source for the pgvector service image so vm0 CI can stop pulling the service container from Docker Hub. Upstream synchronization remains manual, keeping new upstream code behind review before it reaches CI.
Verification
0.8.5from bothMakefileandDockerfilegit diff --checkgo run github.com/rhysd/actionlint/cmd/actionlint@v1.7.7 .github/workflows/docker-publish.ymlRollout
Merge this PR first. Its
masterpush will publish the initial multi-arch image. After the GHCR manifest and anonymous pull access are verified, a companion vm0 PR can pin the published digest in thebench-api,test-migrate, andtest-apiservice definitions.