stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Gate release candidates on tested, verifiable artifacts #339

New Issue
Closed
opened 2026-08-08 20:29:57 +00:00 by timmy · 0 comments
timmy commented 2026-08-08 20:29:57 +00:00
Owner
Copy Link

Evidence

At origin/main (9e68382), .gitea/workflows/release.yml publishes independently of CI and the latest 10 releases contain zero downloadable assets. .gitea/workflows/ci.yml tests separately and archives only frontend/. release/manifest.json is stale/malformed. Historical title scan across 172 issues and 163 PRs found no prior CI-gated artifact-provenance slice; #16/#17 only restored tag/release creation.

User impact

Operators should only receive an RC after the exact commit passes tests, with a deterministic deployable bundle, manifest, and checksum attached for verification. Failed or tampered builds must never be advertised as releasable.

Acceptance tests

  • A deterministic packager emits the runtime app bundle, valid manifest, and SHA-256 checksum for the tested commit.
  • Rebuilding identical input produces identical bytes; changing runtime input changes the digest.
  • Release promotion depends on successful test and package jobs for the same SHA.
  • Promotion verifies the downloaded artifact before creating its tag/release.
  • The resulting Gitea RC targets the merge commit and exposes the bundle, manifest, and checksum as assets.
  • API or integrity failures fail closed; the full test suite remains green.
## Evidence At `origin/main` (`9e68382`), `.gitea/workflows/release.yml` publishes independently of CI and the latest 10 releases contain zero downloadable assets. `.gitea/workflows/ci.yml` tests separately and archives only `frontend/`. `release/manifest.json` is stale/malformed. Historical title scan across 172 issues and 163 PRs found no prior CI-gated artifact-provenance slice; #16/#17 only restored tag/release creation. ## User impact Operators should only receive an RC after the exact commit passes tests, with a deterministic deployable bundle, manifest, and checksum attached for verification. Failed or tampered builds must never be advertised as releasable. ## Acceptance tests - A deterministic packager emits the runtime app bundle, valid manifest, and SHA-256 checksum for the tested commit. - Rebuilding identical input produces identical bytes; changing runtime input changes the digest. - Release promotion depends on successful test and package jobs for the same SHA. - Promotion verifies the downloaded artifact before creating its tag/release. - The resulting Gitea RC targets the merge commit and exposes the bundle, manifest, and checksum as assets. - API or integrity failures fail closed; the full test suite remains green.
timmy closed this issue 2026-08-08 20:37:36 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#339
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?