chore(distribution): record AppImageHub as a channel - #471
Merged
Conversation
The submission is open as AppImage/appimage.github.io#3861 and its review CI is green against 0.13.3, so the inventory now carries the channel it will become. Pending rather than live until it merges, tier 4, and pin strategy none - not because a version is hard to read there, but because there is no served version at all: the catalog holds one line naming this repository and re-reads the releases API on every rebuild, so no release ever bumps anything for it. What the listing does depend on is written into the note, because it is not obvious: the review CI runs the submitted AppImage under firejail --appimage on ubuntu-22.04, and that sandbox is what caught both AppImage defects this release pair fixed - the GLIBC_2.38 floor and the 0770 AppRun.wrapped mode. Both are now gated in the build, and the note names those gates so a future maintainer knows what keeps the listing alive.
|
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
1 participant
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
Adds
appimagehubtodistribution/channels.yamland regenerates thedocs/CHANNELS.mdmatrix (32 channels -> 33, pending 7 -> 8).Why now
The submission is open as AppImage/appimage.github.io#3861 and its review CI is green against 0.13.3 (
NUMBER_OF_WINDOWS: 3,Screenshot taken,* * * SUCCESS * * *).status: pendinguntil it merges.The two shape decisions
kind: curated-catalog,update.method: upstream_pr,sla: on_demand. One PR, then nothing per release: the catalog holds a single line naming this repository, and their worker re-reads the releases API on every rebuild, taking the first AppImage asset matching x64. It is the rare channel with no recurring maintenance cost at all.pin.strategy: none- not because the version is awkward to read there, but because there is no served version to read. The catalog page tracks whatever the newest release holds.What the note records
The listing does not depend on a version, it depends on the AppImage staying startable for someone other than its builder. Their review CI runs the submitted image under
firejail --appimageonubuntu-22.04, and that sandbox caught both AppImage defects this release pair fixed:AppRun.wrappedat0770 root:root(fix(desktop): the AppImage shipped a launcher only its builder could execute #470, 0.13.3) -Permission deniedunder any mount that applies real permission checksBoth are now gated in the build (
tests/unit/desktop-appimage-portability.test.ts,scripts/check-appimage-perms.mjs), and the note names those gates so a future maintainer knows what keeps the listing alive rather than rediscovering it from a red PR upstream.Verification
format,lint,typecheck,knip,readme:check,test(33/33 groups),build.distribution:checkafter the 0.13.3 release: everyevery_releasetier 0/1 channel OK at 0.13.3 (github-release, docker-ghcr, docker-hub-mirror, npm, helm, homebrew, snap); the new row renders SKIP, which is what a channel with no pin should render.