ci: release automation workflow (dispatch + dry-run) - #19
Open
Tagar wants to merge 1 commit into
Open
Conversation
Codifies py4j-python/release_process.md as a manual-dispatch GitHub Action. - build job (always runs, never publishes): JDK 8 zulu + Python, runs ./gradlew clean buildPython (sdist+wheel, bundling jar + docs), twine check, mvn package, uploads dist as artifacts. Fully exercisable on a fork. - publish-pypi (dry_run=false only): PyPI Trusted Publishing (OIDC), no token. - publish-maven (dry_run=false only): mvn deploy + GPG to Sonatype. dry_run defaults to true so the workflow is safe to rehearse. Header documents the required repo config and flags the OSSRH -> Central Portal sunset caveat for the Maven side. Eclipse update-site step is left manual by design. Co-authored-by: Isaac <no-reply@databricks.com>
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.
Release automation (
release.yml)Codifies the manual
py4j-python/release_process.mdinto a single manual-dispatchGitHub Action. byteoak testing PR — validates that the build path
(
./gradlew buildPython,twine check,mvn package) runs green in CI beforeproposing this upstream.
Design
workflow_dispatchwith adry_runinput (defaulttrue).buildjob — always runs, publishes nothing. JDK 8 (zulu) + Python, runs./gradlew clean buildPython(sdist + wheel, which bundle the Java jar anddocs),
twine check,mvn package, and uploads the distributions as workflowartifacts. This is the part we exercise on byteoak.
publish-pypijob — only ondry_run=false. Uses PyPI TrustedPublishing (OIDC) — no stored token.
publish-mavenjob — only ondry_run=false.mvn deploy+ GPG signingto Sonatype.
Owner setup needed before a real (
dry_run=false) runpypienvironment.OSSRH_USERNAME,OSSRH_TOKEN,MAVEN_GPG_PRIVATE_KEY,MAVEN_GPG_PASSPHRASE.Known caveat (documented in the workflow header)
The current
pom.xmldeploys vianexus-stagingtooss.sonatype.org(legacyOSSRH). Sonatype is retiring OSSRH for the Central Publisher Portal; the Maven
deploy may need the
central-publishing-maven-plugin. Thedry_runpath doesnot touch Sonatype, so this is safe to iterate on. The Eclipse update-site step
(
release_process_for_eclipse.md) is intentionally left manual.Scope
Independent of the version-bump PR (#18) — this only adds a workflow file.