fix(ci): revert action bumps in maven-publish workflow#105
Open
Gabrielpanga wants to merge 1 commit into
Open
Conversation
The same major action bumps that broke Build & Test (#85 setup-java v1->v5, #90 dopplerhq/cli-action v1->v4) also landed in maven-publish.yml, but #103 only fixed maven.yml. dopplerhq/cli-action@v4 is not on the repo's allowed-actions list (only @v1), so the publish workflow fails at startup and v1.12.0 never deploys to GitHub Packages. Revert both actions to @v1, matching the last known-good publish (v1.11.0). checkout stays at @v4 (GitHub-owned, allowed).
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.
Summary
Revert
actions/setup-javav5 → v1 anddopplerhq/cli-actionv4 → v1 inmaven-publish.yml, matching the last known-good publish (v1.11.0).Why
#103 fixed the same major action bumps in
maven.ymlbut missedmaven-publish.yml, which the bumps (#85, #90) also touched.dopplerhq/cli-action@v4isn't on the repo's allowed-actions list (only@v1), so the publish workflow fails at startup — that's why v1.12.0 was tagged/released but never deployed to GitHub Packages.Next step after merge
Re-dispatch the publish:
gh workflow run maven-publish.yml -f tag_version=v1.12.0(workflow_dispatch uses the workflow definition frommaster, so this fix must land first).Test plan
maven-publish.ymlis byte-identical to the last green publish (v1.11.0)