Skip to content

chore(opencode): add hardened prerelease pipeline #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
777genius wants to merge 4 commits into
base: dev
Choose a base branch
from
Draft

chore(opencode): add hardened prerelease pipeline #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
06aa804
ci(release): add hardened OpenCode prerelease pipeline
777genius Aug 13, 2026
0ecb49e
fix(release): extract zip assets portably
777genius Aug 13, 2026
a32c435
fix(release): harden hosted approval prerelease
777genius Aug 14, 2026
ad49b4a
build(opencode): repin hosted approval artifact
777genius Aug 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitattributes
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
.github/hardened/*.patch -whitespace
16 changes: 16 additions & 0 deletions .github/hardened/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Hardened OpenCode CLI prerelease

This directory freezes the reviewed patch used by the isolated hardened release
workflow. The patch is applied to base commit
`826d9ad46a22bef0294998e08daa3c4904fea28f`; its resulting tree must equal source
commit `94540b2cbd116bb5bcd6c9ac8f4734f3df637a2b`.

The workflow intentionally produces a draft prerelease that is never production
eligible. It does not replace or modify the upstream publish workflow. Release
mutation occurs only after identity, reproducibility, native execution, manifest,
and provenance gates pass. A protected `hardened-release` GitHub environment must
require reviewer approval.

The full five-platform build and native verification matrix is CI-only. Local
validation covers the immutable patch, script tests, YAML parsing, and static
workflow policy; it is not evidence that foreign-platform binaries execute.
Loading
Loading