You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor(release): sign releases as this repository with the shared publish action #289
Publish this repository's releases with the composite actions/publish-app action from devantler-tech/.github, so they are signed by this repository's own release workflow on its release tag, instead of the shared reusable publisher.
Blocked by
The composite publish action in devantler-tech/.github.
The platform trusting this repository's own release tags.
Scoping note: what the switch touches (main at 8e6f7f0)
Recorded so the next attempt starts from the full surface rather than cd.yaml alone:
cd.yaml: the reusable publish-app.yaml call becomes a job that checks out the tag (persist-credentials: false) and runs actions/publish-app; enable-caller-pin goes away.
Pin-only checks to delete: the publish-pin-approved job and its ci-required-checks entry; scripts/publish-pin-approved.sh and its test; the Dependabot ignore for publish-app.yaml; the .templatesyncignore rows; the scaffold's tenant-only removal list and scaffold.test.sh.
Contract tests to re-target, not delete:scripts/workflow-caller-pin-contract.test.sh (it also guards the release.yaml and template-sync.yaml pins, so the workflow-caller-pins job stays and pins the action by SHA instead), scripts/platform-tenant-envelope.test.sh and scripts/workflow-caller-contract.test.sh assert the shared-publisher signing subject and enable-caller-pin. They must assert the own-release subject (this repository's cd.yaml on refs/tags/v…) instead, so the supply-chain check stays as strong.
Docs: README and docs/REFERENCE.md describe the pin-approval job.
Suggested order: this PR first on main (default app-manifest works with today's deploy/deployment.yaml), then #288 rebases and sets app-manifest: base/deployment.yaml.
The current starter envelope check rejects the minimal direct publisher that the portable guard already admits. I reproduced the rejection against current template main and am preparing that prerequisite first: validate the direct producer through the existing strict execution-frame guard and the platform's exact own-release matcher. Shared-only rules, explicit shared-revision rules, environment overrides and branch publication remain rejected.
This slice keeps the starter publisher and every required check unchanged. The actual caller switch and signed release/reconciliation proof remain on #289.
Implementation first started on 2026-11-15, evidenced by the validated signed draft #296. Project 5 now reflects the actual In Progress work and preserves that first-start date. This is finishing the shared prerequisite for the parked deployment changes, not a new Ready pull; current stage saturation holds further starts. The caller switch and real signed-release/reconciliation acceptance remain unfinished.
Activity
devantler commentedon Nov 15, 2026
Scoping note: what the switch touches (
mainat8e6f7f0)Recorded so the next attempt starts from the full surface rather than
cd.yamlalone:cd.yaml: the reusablepublish-app.yamlcall becomes a job that checks out the tag (persist-credentials: false) and runsactions/publish-app;enable-caller-pingoes away.publish-pin-approvedjob and itsci-required-checksentry;scripts/publish-pin-approved.shand its test; the Dependabot ignore forpublish-app.yaml; the.templatesyncignorerows; the scaffold's tenant-only removal list andscaffold.test.sh.scripts/workflow-caller-pin-contract.test.sh(it also guards therelease.yamlandtemplate-sync.yamlpins, so theworkflow-caller-pinsjob stays and pins the action by SHA instead),scripts/platform-tenant-envelope.test.shandscripts/workflow-caller-contract.test.shassert the shared-publisher signing subject andenable-caller-pin. They must assert the own-release subject (this repository'scd.yamlonrefs/tags/v…) instead, so the supply-chain check stays as strong.docs/REFERENCE.mddescribe the pin-approval job.Suggested order: this PR first on
main(defaultapp-manifestworks with today'sdeploy/deployment.yaml), then #288 rebases and setsapp-manifest: base/deployment.yaml.fix(release): reject workflow-level publisher overrides
fix(release): prepare tenants for own release signing (#288)
chore: agent-claim #289 nonce=da57ea1d0d46d38a36ce3c68de67b50b
devantler commentedon Nov 15, 2026
The current starter envelope check rejects the minimal direct publisher that the portable guard already admits. I reproduced the rejection against current template main and am preparing that prerequisite first: validate the direct producer through the existing strict execution-frame guard and the platform's exact own-release matcher. Shared-only rules, explicit shared-revision rules, environment overrides and branch publication remain rejected.
This slice keeps the starter publisher and every required check unchanged. The actual caller switch and signed release/reconciliation proof remain on #289.
Implementation first started on 2026-11-15, evidenced by the validated signed draft #296. Project 5 now reflects the actual In Progress work and preserves that first-start date. This is finishing the shared prerequisite for the parked deployment changes, not a new Ready pull; current stage saturation holds further starts. The caller switch and real signed-release/reconciliation acceptance remain unfinished.
chore: agent-claim #289 nonce=7b331b3e65cd4a81242aaf0eef3a3461
chore: agent-claim #289 nonce=2b03cc1e7061b1296d914bb70ddeeed6
chore: agent-claim #289 nonce=48ae2606547001d3abee88ee7f65e5a6
fix(publishing): validate application-owned release signers (#296)