feat: add native app-image launcher distribution#172
Open
golemcore1 wants to merge 1 commit intomainfrom
Open
Conversation
|
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.
Summary
This PR introduces a native local distribution path for GolemCore Bot and makes the launcher behavior consistent across staged updates, bundled app-image runtime jars, and the legacy classpath fallback.
At the packaging level, the release workflow now builds platform-specific native app-image bundles in addition to the executable JAR and publishes those archives together with updated SHA-256 checksums. To support local development and manual packaging, the repository also gains a reusable build script under
.github/scripts/plus annpxentry point that generates the same native archive format locally.At runtime,
RuntimeLauncheris extended so that a native launcher can start the bot using the same self-update model that already exists for the JAR flow. The launcher now resolves runtime in a deterministic order: first a staged update selected throughupdates/current.txt, then the bundled runtime JAR embedded in the app-image, and finally the existing Jib/classpath fallback. This keeps local native bundles compatible with staged updates without introducing a separate execution model.The launcher also now forwards JVM system properties to the spawned runtime process, which is important for operational overrides such as
-Dserver.port=..., storage path overrides, update path overrides, and other JVM-level configuration passed at startup. Spring-style application arguments such as--server.port=...continue to work as before, and the implementation avoids duplicating overrides when both property sources are present.To make the new behavior durable, the test suite for
RuntimeLauncheris expanded to cover bundled runtime resolution, environment/property-based overrides, forwarding of JVM system properties, precedence rules, and the fallback path when no valid bundled runtime JAR is available.Documentation is updated across the README, quick start, deployment guide, and configuration reference so users can understand: