Files
amethyst/orchard.txt
T
Claude 689d5092bb refactor: publish Orchard's Flatpak from the release bundles, drop ghcr
Orchard 0.2.0 installs a .flatpak bundle from an https URL, checked against
the sha256 in the signed asset. The GitHub Release already carries both
bundles, so `amy releases publish` now names them directly, in the same
NIP-82 shape as the desktop files (m=application/vnd.flatpak, f per arch,
one release <id>@<version> on main), and nothing is built or hosted for
Orchard anymore.

- Removed: the CI steps that built orchard-publish and pushed OCI images to
  ghcr with GITHUB_TOKEN (and packages: write), OciRegistry, OrchardConfig,
  --orchard-toml and jackson-dataformat-toml, and desktopApp/packaging/orchard
  (the TOML, description and docker fallback).
- Each bundle is checked by the ref in its header (app id and arch) before
  it is hashed. The listing moves into FlatpakRelease, tag for tag the live
  one.
- Checked against Orchard 0.2.0's own catalog code: the dry-run events for
  the real 1.19.0 x64 bundle project as installable from the GitHub URL with
  the pinned sha256.
- RELEASE_OPS: Orchard is part of the one `amy` run; notes the 1.19.0 image
  on ghcr (keep it until a later release is out) and the stable/master
  branch hop for users who installed that image.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HjWRrkeWh8jtjHeFDRXkc3
2026-10-15 21:47:39 +00:00

6 lines
376 B
Plaintext

# Orchard repository proof (https://github.com/Letdown2491/orchard): Orchard
# shows this repository's link as verified on any listing signed by a key named
# here. One key per line (npub or hex). This is Amethyst's key, the one that
# signs the Orchard and Zapstore listings (RELEASE_OPS.md § Nostr releases).
npub142gywvjkq0dv6nupggyn2euhx4nduwc7yz5f24ah9rpmunr2s39se3xrj0