27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# Distribution plan
|
|
|
|
Lumbridge source and release metadata live in the public Gitea repository. Users
|
|
should not need a Rust toolchain.
|
|
|
|
Initial release artifacts:
|
|
|
|
- macOS arm64: signed and notarized `.dmg` plus a tar archive.
|
|
- macOS x86_64: added when a maintained Intel runner is available.
|
|
- Ubuntu x86_64: `.deb` and AppImage.
|
|
- Omarchy/Arch x86_64: signed package archive and an AUR recipe that downloads
|
|
the matching release artifact.
|
|
|
|
Every package installs the canonical Lumbridge application icon into the native
|
|
platform location: the macOS asset catalog/`.icns`, Linux hicolor PNG sizes and
|
|
`.desktop` entry, and any package-manager metadata. Derived files come from the
|
|
transparent masters in `assets/brand/`; light and dark variants are for product
|
|
surfaces, while launchers use the canonical app icon unless a platform has a
|
|
documented adaptive-icon contract.
|
|
|
|
Each release includes SHA-256 checksums, a signed update manifest, SBOM, license
|
|
notices, and the exact source commit. Reproducibility is a goal, but a release is
|
|
not called reproducible until two clean builders produce matching artifacts.
|
|
|
|
The updater must verify signatures before replacing binaries, retain the prior
|
|
version for rollback, and never update a running session runtime in place.
|