ci: unify publishing via workflow_call in publish.yml #2655
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
hubcio
force-pushed
the
refactor-post-merge
branch
2 times, most recently
from
bf3e0f2 to
dc368bc
Compare
post-merge.yml duplicated Docker building, manifest creation, crate publishing, and tag management that already existed in publish.yml. Maintaining parallel implementations risked drift and complicated adding new components. Refactored publish.yml to accept workflow_call trigger with inputs for component selection and edge mode. post-merge.yml now delegates to publish.yml via call-publish job, preserving exact behavior: - Docker :edge tags always created on merge - Versioned tags only for pre-release versions - :latest never touched by auto-publish
hubcio
force-pushed
the
refactor-post-merge
branch
from
dc368bc to
e2f2348
Compare
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.
post-merge.yml duplicated Docker building, manifest creation,
crate publishing, and tag management that already existed in
publish.yml. Maintaining parallel implementations risked drift
and complicated adding new components.
Refactored publish.yml to accept workflow_call trigger with
inputs for component selection and edge mode. post-merge.yml
now delegates to publish.yml via call-publish job, preserving
exact behavior: