ci: simplify fork prerelease workflow - #18
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
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
Evidence
Pre-release runs 30530565801 and 30451532414 both ended with startup_failure and jobs: []. The affected tags were still published successfully by the separate Build & Publish Docker Image workflow.
The legacy publish-image reusable workflow uses runs-on: build, while the DOS fork publisher uses ubuntu-latest and already publishes to GHCR and Docker Hub.
Validation
The repository Husky hook cannot initialize in a fresh worktree because .husky/_/husky.sh is absent, so the commit used --no-verify after the checks above passed.