Repository navigation
Catch Flatpak sandbox and host breakage in CI before release - #16
Merged
Merged
Conversation
Describe what the Flatpak repackage should be and the workflow for each upstream release, for Claude and Codex: refresh the patches, review the release, get product decisions, verify, then ship within the request.
Launch the built Flatpak headless in the CI container and check where the sandbox meets the host: the host server, agent CLIs on the login PATH, downloads, terminals and git, editors on the host PATH and installed as Flatpaks, SSH, Tailscale, managed policy, database maintenance, and the recovery screen when the host is out of reach. The checks are typechecked TypeScript using Playwright, with setup in tests/packaged and failure screenshots and logs uploaded from CI. scripts/test-packaged runs the same checks locally against a local build or a published commit with Docker or Podman, and the update skill points to it.
Drop the display name label check from 0001 and the pass-through field checks from 0002, keeping the assertions for what each patch changes.
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.
Breakage where the sandbox meets the host, like agents not being found in 0.1.7 or downloads not saving in 0.1.6, only showed up after installing a build by hand. The build's unit tests passed both times.
Validation now installs the built Flatpak in the CI container, launches it headless, and runs checks through the real app: the host server, agents on the login PATH, downloads, terminals and git, editors on the host PATH and as Flatpaks, SSH, Tailscale, managed policy, database maintenance, and the recovery screen when the host is out of reach. Failed checks upload screenshots and logs.
./scripts/test-packagedruns the same checks locally against a local build or a published commit.This also adds the
update-t3codeagent skill for version bumps, which now runs these checks.All checks passed locally with Docker and Podman. Against the published 0.1.7, only the agent check fails.