feat(ci): add release JAR build workflow

[halibobo1205]

User description

What does this PR do?

Adds a manually triggered GitHub Actions workflow for building release JARs from the master branch.

The workflow:

• builds x64 JARs with Temurin JDK 8;
• builds aarch64 JARs with Temurin JDK 17;
• runs smoke tests for FullNode, Toolkit, and ArchiveManifest;
• produces the existing nine release JAR filenames;
• generates SHA-256 checksums and build metadata;
• uploads a combined release artifact.

Why are these changes required?

Release JARs are currently built on developers' local machines. Moving the build process into CI provides a consistent build environment and makes each artifact traceable to its source commit and workflow run.

This PR has been tested by:

• YAML syntax validation
• Gradle release task dry run
• ARM64 release JAR build with Temurin JDK 17
• FullNode, Toolkit, and ArchiveManifest smoke tests
• Nine-JAR artifact assembly and checksum generation

Follow up

GPG signing, GitHub Release publishing, and reproducible builds are outside the scope of this PR.

Extra details

• The workflow can only run from master.
• Intermediate architecture artifacts are retained for one day.
• The final combined artifact is retained for 30 days.
• Artifact overwrite is enabled to support complete workflow reruns.

---

CodeAnt-AI Description

Add a consistent, traceable CI workflow for release JARs

What Changed

• Developers can manually build release JARs from the master branch in GitHub Actions
• The workflow produces x64 and aarch64 versions of FullNode, Toolkit, and ArchiveManifest
• Each JAR is smoke-tested before packaging, and the final artifact includes the standard JAR names
• Build metadata records the source commit, workflow run, architecture, and Java version
• SHA-256 checksums are generated for all release JARs

Impact

✅ Repeatable release builds
✅ Verified x64 and aarch64 JARs
✅ Traceable artifacts with checksums

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	6b1c656	Aug 18, 2026 · 08:13	08:13

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn