Claude bf31a39701 Replace tag-push release workflow with a release-published one ... Root cause: the previous workflow triggered on `push: tags`, which GitHub doesn't reliably fire for tags created through the "Publish release" UI flow, and it created its own draft release rather than attaching to one you publish yourself. It also lacked build provenance attestation for the uploaded assets. Fix: trigger on `release: published` instead (guaranteed to fire), build main.js/manifest.json/styles.css, attest their build provenance, and upload them to the already-published release with `gh release upload --clobber`. Verification: YAML parses cleanly (python -c "yaml.safe_load(...)"). Fixed a stray trailing quote after `--clobber` from the pasted version that would have broken the run script. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018KJkrwy6CLrUh8VkbgvwEt		2026-07-18 14:57:31 +00:00
..
release.yml	Replace tag-push release workflow with a release-published one	2026-07-18 14:57:31 +00:00