Repository navigation
docs(distribution): mark Flathub deprecated and route Flatpak users to FlatPark - #252
Merged
Merged
Conversation
…o FlatPark flathub/flathub#9538 was declined on 2026-07-30 under Flathub's generative AI policy and closed from our side, so the inventory and the docs no longer describe a channel that is coming. - channels.yaml: flathub pending -> deprecated, sla on_demand, first_pr set to #9538, and the note now carries the reason plus the closing comment URL so the decision is auditable from the inventory alone. The flatpark note's "revisit if Flathub is accepted" sequencing question is closed out, and the appimage note no longer implies the repack exists for Flathub. - DISTRIBUTION.md: FlatPark becomes the Flatpak section and owns the sandbox and flatpak-override guidance; a new "Flathub (submission declined)" section states plainly that `flatpak install flathub org.libredb.Studio` will not work and links the policy and the closing comment. Section title, TOC row and both anchors follow. The roadmap item is closed rather than left pending. - README.md: drop the "Flathub listing is in submission" claim, which is no longer true; the Flatpak row below already points at FlatPark. - packaging/flatpak/README.md: status banner at the top; the repack rationale now records that the AI policy ended the review before the repack was ever discussed, so from-source remains an untested and open blocker; the checklist is relabelled as a record of what was done. - packaging/flatpark/README.md: the Flathub disclosure step and the relationship section reflect the outcome. The directory itself stays: flatpak-smoke.yml still builds the AppImage and repacks it, which is real coverage of the desktop artifact. Also corrects two claims that had drifted independently: the ci_enabled section used `appimage` as its "pending" example although that channel is live, and there was no worked example of when `deprecated` applies.
…Flathub Comment-only. Both workflows explained the desktop artifacts and their release gate in terms of a Flathub listing that will not exist, which would mislead whoever next asks whether the AppImage is still needed. - release-artifacts.yml: the AppImage is the Linux desktop download in its own right, not an input to a Flathub repack; the hard release gate and the SLSA attestation are justified accordingly. FlatPark's claim on the GUI .deb is unchanged and still the reason the .deb cannot drift from the tag. - flatpak-smoke.yml: flathub/org.libredb.Studio was never created, so there is no External Data Checker bumping it. Records that this job is now the only consumer of packaging/flatpak/ and is kept as AppImage coverage. No behaviour change: both files parse identically and the diff contains no non-comment lines.
|
This was referenced Jul 30, 2026
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
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.
What
flathub/flathub#9538 was declined on 2026-07-30 under Flathub's generative AI policy and closed from our side (closing comment). This stops the inventory and the docs describing a channel that is not coming, and routes every Flatpak instruction to FlatPark, which is live.
Docs and inventory only. No source, no workflow, no packaging descriptor changes.
Changes
distribution/channels.yaml—flathubgoespending->deprecatedwithsla: on_demandandfirst_prpointing at #9538. The note carries the reason and the closing-comment URL, so the decision is auditable from the inventory alone. Theflatparknote's open "revisit if Flathub is accepted" sequencing question is closed out, and theappimagenote no longer implies the AppImage repack exists for Flathub's benefit.docs/DISTRIBUTION.md— FlatPark becomes the Flatpak section and owns the sandbox andflatpak overrideguidance that previously sat under Flathub. A new### Flathub (submission declined)section states plainly thatflatpak install flathub org.libredb.Studiowill not work, and links the policy and the closing comment. Section title, TOC row and both anchors follow. The roadmap item is closed rather than left pending.README.md— drops the "Flathub listing is in submission" claim, which is no longer true. The Flatpak row directly below already points at FlatPark.packaging/flatpak/README.md— status banner at the top. The repack rationale now records how the review actually went: the AI policy ended it before the repack was ever discussed, so the from-source requirement remains an untested and open blocker rather than a settled one. The submission checklist is relabelled as a record of what was done.packaging/flatpark/README.md— the Flathub disclosure step and the relationship section reflect the outcome.packaging/flatpak/stays in the tree:flatpak-smoke.ymlstill builds the AppImage and repacks it with that manifest, which is real coverage of the desktop artifact. Removing it would cost coverage and gain nothing.Drive-by corrections
Two claims in
DISTRIBUTION.mdhad drifted independently of this change:ci_enabledsection usedappimageas its example of apendingchannel, but that channel islive— replaced withwinget, which is genuinely pending;deprecatedapplies, which is exactly the gap this PR fills.Verification
formatOK,lintOK (0 errors, 73 pre-existing warnings),typecheckOK,knipOK,bun run testOK (2862 + 306 pass, all 20 component groups),distribution:check --strictexits 0, andtests/unit/distribution-check.test.tspasses 51/51 against the edited inventory.bun run buildwas not run: this branch changes only.mdand.yamlfiles, and the worktree it was authored in uses a symlinkednode_moduleswhere the Next.js build is not reliable. CI runs it.