ci: release.yaml triggers on product paths only #10

Merged

beddari merged 1 commit from release-trigger into main

2026-09-17 19:44:14 +00:00

beddari commented

2026-09-17 19:43:41 +00:00

Owner

A change to the Makefile, go.work, or the workflow itself no longer starts a release job; the next product change exercises it, and a release is identified by the product commit it was built from. Until Sentral has code, nothing is queued for the fabrikk-release runner that does not exist yet. The release-model page and the README follow-up note say the same.

Protected path changed: .forgejo/. Human review required; no attestation tag, so validate-attestation fails by design.

A change to the `Makefile`, `go.work`, or the workflow itself no longer starts a release job; the next product change exercises it, and a release is identified by the product commit it was built from. Until Sentral has code, nothing is queued for the `fabrikk-release` runner that does not exist yet. The release-model page and the README follow-up note say the same. Protected path changed: `.forgejo/`. Human review required; no attestation tag, so `validate-attestation` fails by design.

beddari added 1 commit

2026-09-17 19:43:41 +00:00

ci: release.yaml triggers on product paths only

validate-attestation / validate (pull_request) Failing after 2m52s

Details

32157b7208

A change to the Makefile, go.work, or the workflow itself no longer starts a release job; the next product change
exercises it, and a release is identified by the product commit it was built from. Until Sentral has code, nothing
is queued for the fabrikk-release runner that does not exist yet.

beddari merged commit d2bdf65c7b into main

2026-09-17 19:44:14 +00:00

beddari deleted branch release-trigger

2026-09-17 19:44:14 +00:00

beddari referenced this pull request from a commit

2026-09-17 19:44:14 +00:00

Merge pull request 'ci: release.yaml triggers on product paths only' (#10) from release-trigger into main