ci: manual build+push of the latest main image (workflow_dispatch)#524
Closed
Zheaoli wants to merge 1 commit into
Closed
ci: manual build+push of the latest main image (workflow_dispatch)#524Zheaoli wants to merge 1 commit into
Zheaoli wants to merge 1 commit into
Conversation
The latest-image workflow only triggered on `v*` tag pushes, so deploying the current main meant cutting a tag. Add a `workflow_dispatch` trigger so it can be run manually from the chosen branch (default main) to build and push the multi-arch `:latest` image on demand. This workflow pushes a hardcoded `:latest` tag and does not use the `Get Version` step's output, so a manual (non-tag) run needs no version handling — `:latest` is built from the selected branch's code as-is. The existing tag trigger is unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
Closing — this is Impl's CI lane and they're already on it with a cleaner version (also removes the vestigial Get Version step). Superseded by their upcoming PR. |
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
1 participant
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.
What
Adds a
workflow_dispatchtrigger tobuild-main.yamlso the multi-arch:latestimage can be built and pushed manually from the chosen branch (default main), without cutting av*tag first. Scope per request: just manually build+push a main image (same buildx → Docker Hub flow; no server-deploy step added).Notes
:latesttag and does not consume theGet Versionstep's output, so a manual (non-tag) run needs no version handling — the deprecated${GITHUB_REF#refs/tags/}would resolve to a branch ref on dispatch, but it's unused here, so:latestis simply built from the selected branch's code. (Left the unused step as-is to keep this change minimal; can remove separately if desired.)v*tag trigger is unchanged.build-release.yaml(the versioned image): a manual run there would need a version input since its tag does useGet Version. Out of scope unless wanted.