ci(web): attach the Samsung TV package to a release - #44
Merged
Merged
Conversation
A TV owner installs the client from a release asset: Apps2Samsung reads this repository's releases for punktfunk-tizen-<version>.wgt, and the CLI route on the install page downloads the same file. The build job now makes the package from the wasm it already built and a v* tag attaches it beside the tarball. Unsigned, so the job needs no Tizen SDK.
enricobuehler
changed the base branch from
tizen/t2-tunnel-and-packaging
to
main
October 2, 2026 22:51
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.
T5 of
design/tizen-client-implementation-plan.md, the CI piece. Stacked on #42 (retargets tomainwhen that merges).The
buildjob runsnpm run build:tizen -w punktfunk-webafternpm run build(the wasm is reused), uploadspunktfunk-tizenas a run artifact, and av*tag attachespunktfunk-tizen-<version>.wgtto the release beside the tarball. Unsigned, as §6 says to try first: a set only installs a package signed for its own DUID, so each owner signs their copy and this job needs no Tizen SDK. The asset name is what the Apps2Samsung catalog entry matches.Still outside this PR, per the plan: proving the unsigned zip through Apps2Samsung once, the catalog PR (an outward publish, maintainer's yes), and the
samsung-tv.mdinstall page (monorepo docs-site). The send-log diagnostics line landed in #42.?ui=,_e2eand_screenswere never in the packaged build: Vite's single entry isindex.html, and the other two pages are reached only on the dev server.🤖 Generated with Claude Code
https://claude.ai/code/session_01AMdVnA5hEykPfKrc5UByY7
Generated by Claude Code