ci: publish the PyPI wheel from release-pypi.yml after Java Release succeeds - #224
Merged
Conversation
…ucceeds The PyPI Trusted Publisher for codeanalyzer-java is bound to the workflow file release-pypi.yml and the pypi environment, so the publish step cannot live in release.yml (v3.0.2 failed there with invalid-publisher). The wheel is now built from the released codeanalyzer.jar asset, in a workflow_run job that fires when Java Release succeeds; a release created with GITHUB_TOKEN would not trigger release: published. workflow_dispatch re-publishes a tag on demand. Refs #222
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.
Refs #222
The PyPI Trusted Publisher is bound to
release-pypi.yml+ thepypienvironment, so v3.0.2's publish step inrelease.ymlfailed withinvalid-publisher.release-pypi.yml:workflow_runon "Java Release" success (aGITHUB_TOKEN-created release never firesrelease: published), downloads the releasedcodeanalyzer.jar, builds the wheel, publishes underenvironment: pypi.workflow_dispatchwith a tag re-publishes on demand.release.yml: publish steps andid-tokenremoved; version check and release notes unchanged.After merge: move tag
v3.0.2to the new main and re-push to rerun both.