Skip to content

ci: publish JavaAPI/ByteCodeTranslator release jars from parparvm workflow#4568

Merged
shai-almog merged 1 commit intomasterfrom
codex/add-javaapi.jar-and-bytecodetranslator.jar-to-release
Feb 24, 2026
Merged

ci: publish JavaAPI/ByteCodeTranslator release jars from parparvm workflow#4568
shai-almog merged 1 commit intomasterfrom
codex/add-javaapi.jar-and-bytecodetranslator.jar-to-release

Conversation

@shai-almog
Copy link
Collaborator

Motivation

  • Make release jar publishing the responsibility of the workflow that builds ParparVM artifacts instead of coupling it to the JavaDocs workflow.
  • Avoid mixing JavaDocs logic and VM build/publish logic so each workflow has a single clear purpose.

Description

  • Removed the JavaAPI/ByteCodeTranslator release build and attach steps from .github/workflows/javadocs.yml so that file only handles JavaDocs (CodenameOne/javadocs.zip).
  • Updated .github/workflows/parparvm-tests.yml to trigger on release.published and added a new release-jars job.
  • The release-jars job checks out the repo, sets up JDK 8 (actions/setup-java@v4), runs mvn -B -f vm/JavaAPI/pom.xml package and mvn -B -f vm/ByteCodeTranslator/pom.xml package, verifies the produced jars exist, and attaches them to the GitHub release using softprops/action-gh-release@v1.
  • The job includes contents: write permission and uses a Maven cache on the JDK 8 setup step.

Testing

  • Verified both modified workflow YAML files parse successfully with Ruby via ruby -e "require 'yaml'; YAML.load_file('.github/workflows/javadocs.yml'); YAML.load_file('.github/workflows/parparvm-tests.yml'); puts 'ok'", which returned ok.

Codex Task

@github-actions
Copy link

✅ Continuous Quality Report

Test & Coverage

Static Analysis

Generated automatically by the PR CI workflow.

@shai-almog shai-almog merged commit bc7ec47 into master Feb 24, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant