RICOCHET
Production distribution

Store Packaging

Store-ready release inputs, metadata validation, and marketplace handoff rules for production Ricochet packages.

docs/reference/guides/store-packaging.html
docs/wiki/store-packaging.html
Ricochet stack and MVC flow Value::String Value::Map Value::Class Value::Block bytecode VM Controller View Postgres $name "home/index" swap view [ ... ] "methodName" Method
← Back to Guides Portal

Ricochet publishes store-ready release inputs, not marketplace account uploads. The repository-owned boundary is packaging, metadata, signing, notarization, checksums, manifests, and update-channel metadata. Microsoft Partner Center, Apple App Store Connect, Flathub, Snapcraft, and distro repository uploads stay operator-owned because they require external publisher accounts, review flows, and account-specific legal metadata.

Supported Release Inputs

Windows releases provide a portable ZIP, an NSIS setup executable, Authenticode signing for production tags, an artifact manifest, a signing report, and checksums.

Linux releases provide a portable tarball, a Debian package, desktop launcher metadata, SVG icon, AppStream metainfo, changelog, maintainer metadata, bundled docs/examples/packages, detached GPG signatures for production tags, a manifest, a signing report, and checksums.

macOS releases provide Apple Silicon and Intel tarballs, codesigned binaries, accepted notarization reports for production tags, manifests, signing reports, notary reports, and checksums.

Store Readiness Gate

Run the store packaging validator after artifact manifest validation:

pwsh -NoProfile -File ./scripts/validate-store-packaging.ps1 `
  -Target windows-x64 `
  -PackageVersion 0.1.19-rc.3

pwsh -NoProfile -File ./scripts/validate-store-packaging.ps1 `
  -Target linux-x64 `
  -PackageVersion 0.1.19-rc.3

pwsh -NoProfile -File ./scripts/validate-store-packaging.ps1 `
  -Target macos-arm64 `
  -PackageVersion 0.1.19-rc.3

Add -RequireProduction for production tag artifacts. That rejects dry-run, skipped, or unsigned fallback signing reports and requires the production signing/notarization state for the target.

The release workflow runs this validator for every platform package before uploading artifacts. It inspects Windows ZIP contents and installer presence, Linux tarball metadata and Debian package metadata, and macOS tarball contents plus accepted notarization reports for production tags.

Marketplace Submission

Marketplace submission starts from the validated GitHub release artifacts. Windows uses the signed installer or a future Partner Center/MSIX pass tied to the publisher identity. Linux uses the Debian package and AppStream metadata for apt repositories or as source material for Flathub/Snapcraft packaging. macOS uses the signed and notarized tarballs for direct distribution; a Mac App Store SKU would need a separate sandboxed bundle, entitlements, product identity, and App Store Connect submission flow.

Do not publish marketplace artifacts that failed manifest validation, store-packaging validation, signature verification, or update-channel validation.