docs: record the promotion as finished, and the rough edges it left - #86
Merged
Conversation
Everything this runbook was tracking is now real: Ghostty publishes to the remote, both apps install from it, the site lists them, and expected-apps.json turns the sanity check from a warning into a gate. Checks off what happened and links where. One prediction in here was wrong and is corrected rather than quietly dropped: the GHCR package came out public on first push, so the manual visibility flip this document warned about was not needed. Recorded as "re-check rather than assume" instead of "not a problem", since a private package and a missing one fail identically and the next app may land the other way. Adds a rough-edges section for three things found while finishing this that are real but out of scope: Test can never pass here (upstream's namespace-profile-ghostty-* runners don't exist in this org, so those jobs queue forever and cannot gate a merge), publish-flatpak.yml is still a vendored copy outside the org's drift check, and ghcr.io/tuna-os/blueshell has no plain :latest tag. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EMBRswEeeX2kzVSwpbxCoy
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.
Everything
docs/TUNA_OS_PROMOTION.mdwas tracking is now real:app/com.mitchellh.ghostty/{x86_64,aarch64}/masterexpected-apps.jsonturns the sanity check from a standing warning into a gate (chore(flatpak): expect BlueShell and Ghostty in the remote docs#374)hanthor/blueshellarchived, its PR closedOne prediction in the doc was wrong
It warned that
ghcr.io/tuna-os/ghosttywould be created private and need a manual visibility flip. It came out public on first push — verified by an anonymous GHCR token pull returning 200 forlatest,latest-x86_64andlatest-aarch64.Corrected as "re-check rather than assume" rather than deleted: a private package and a missing one fail identically, so the next app is still worth checking.
New: rough edges found while finishing this
Three real problems, all out of scope, recorded so they aren't rediscovered:
Testcan never pass in this repo. Upstream'stest.ymlruns onnamespace-profile-ghostty-*runners — Namespace.so machines the tuna-os org doesn't have. Those jobs queue indefinitely, so "Required Checks: Test" is permanently pending on every PR and cannot function as a merge gate.ptyxis-testsis the suite that actually runs.publish-flatpak.ymlis still a vendored copy of the org pipeline, outsidetuna-os/.github's drift check. Tracked in Migrate publish-flatpak.yml onto the shared tuna-os pipeline #85.ghcr.io/tuna-os/blueshellhas no plain:latesttag — the vendored workflow pushes onlylatest-<arch>. Harmless for flatpak, but a plain pull of that path 404s whileghcr.io/tuna-os/ghostty:latestworks.🤖 Generated with Claude Code
https://claude.ai/code/session_01EMBRswEeeX2kzVSwpbxCoy