Packaging and Releases

Packaging and Releases

RayoMD's default packages keep the native path dependency-light.

Artifact	Contents
rayomd-<version>-windows-x64.zip	Windows Dear ImGui app and CLI modes in rayomd.exe
rayomd-<version>-linux-x64.tar.gz	Portable Linux CLI without a libcurl runtime dependency
rayomd-<version>-linux-x64-curl.tar.gz	Linux CLI with HTTP/HTTPS image fetching through libcurl

The release workflow publishes packages when VERSION changes on master, for a matching v<VERSION> tag, or through manual dispatch. Manual reruns replace the release files for that version.

Lightweight-package boundary

• Do not bundle a browser, Node.js, LaTeX, or Pandoc into the native package.
• Pandoc is an optional Windows compatibility path and has separate GPL licensing/deployment considerations.
• The default Linux artifact avoids libcurl ABI and distro-baseline problems.
• The curl build is separate so URL-image support remains an explicit choice.
• Reversible PDFs add no mandatory runtime dependency.

Release contents, versioning rules, and verification commands are maintained in CONTRIBUTING.md, VERSION, and the release workflow.

RayoMD's own code is Apache-2.0. Dear ImGui retains its license. Do not create a larger compatibility package without reviewing every bundled dependency and its redistribution terms.