Skip to content

ci(web): attach the Samsung TV package to a release - #44

Merged
enricobuehler merged 1 commit into
mainfrom
tizen/t5-ship
Oct 2, 2026
Merged

enricobuehler merged 1 commit into
mainfrom
tizen/t5-ship

Conversation

@enricobuehler

Copy link
Copy Markdown
Contributor

T5 of design/tizen-client-implementation-plan.md, the CI piece. Stacked on #42 (retargets to main when that merges).

The build job runs npm run build:tizen -w punktfunk-web after npm run build (the wasm is reused), uploads punktfunk-tizen as a run artifact, and a v* tag attaches punktfunk-tizen-<version>.wgt to 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.md install page (monorepo docs-site). The send-log diagnostics line landed in #42. ?ui=, _e2e and _screens were never in the packaged build: Vite's single entry is index.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

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
enricobuehler changed the base branch from tizen/t2-tunnel-and-packaging to main October 2, 2026 22:51
@enricobuehler
enricobuehler merged commit 4e2d7c3 into main Oct 2, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant