chore: add workflow_dispatch to release workflow for manual republish#109
Merged
chore: add workflow_dispatch to release workflow for manual republish#109
Conversation
Allows manually triggering build+publish for an existing release tag when the automated pipeline fails (e.g. the v1.3.3 Docker image issue).
b401a0e to
60b92de
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #109 +/- ##
=======================================
Coverage 95.63% 95.63%
=======================================
Files 8 8
Lines 1719 1719
=======================================
Hits 1644 1644
Misses 75 75 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
workflow_dispatchtrigger with ataginput to the release workflowWhy
v1.3.3 failed to publish because the pypi-publish action was pinned to a commit SHA with no Docker image. The fix is on main (#107) but re-running the old workflow replays the broken YAML. This dispatch trigger lets us run the current workflow against the v1.3.3 tag.
After merge
Run from the Actions tab:
release-please>Run workflow> tag:v1.3.3