Skip to content

[Java][Python][TypeScript] Optional macOS release binaries - #735

Open
teodordelibasic-db wants to merge 1 commit into
mainfrom
release/macos-binaries
Open

[Java][Python][TypeScript] Optional macOS release binaries#735
teodordelibasic-db wants to merge 1 commit into
mainfrom
release/macos-binaries

Conversation

@teodordelibasic-db

Copy link
Copy Markdown
Collaborator

What changes are proposed in this pull request?

WHAT: Two related release-tooling changes.

  • Bump central-publishing-maven-plugin from 0.5.0 to 0.11.0 in java/pom.xml. 0.5.0 crashes while polling Maven Central Portal after a successful upload because the Portal status response now includes a warnings field the old plugin cannot parse.
  • Add an optional macos-binaries-release input to the Java, JNI, Python, and TypeScript builder workflows. When set, the workflow downloads laptop-built macOS artifacts from that GitHub Release and uploads them alongside the CI-built linux/windows artifacts. Leave the input empty to skip macOS, which is the default.

WHY: There are no macOS CI runners, so Apple binaries have to be built on a laptop and attached to a (draft) GitHub Release before the builder runs. The Java publisher job has also been going red on every recent release after the bundle was already uploaded, because of the 0.5.0 plugin parse error.

How is this tested?

Not tested. The plugin bump is a version pin; the new workflow jobs only run when macos-binaries-release is set, which is not exercised by pull-request CI.

Signed-off-by: teodordelibasic-db <teodor.delibasic@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant