Skip to content

Fix immutable-release preflight permission boundary - #2

Merged
moloch-- merged 3 commits into
mainfrom
feat/immutable-preflight-fix
Aug 26, 2026
Merged

moloch-- merged 3 commits into
mainfrom
feat/immutable-preflight-fix

Conversation

@moloch--

Copy link
Copy Markdown

Summary

The v0.0.1 tag build stopped before signing because GitHub documents the immutable-releases settings endpoint as requiring repository Administration read permission. A workflow GITHUB_TOKEN cannot receive that permission, so the endpoint returned 403 Resource not accessible by integration.

Keep the actual security boundary explicit:

  • immutable releases remain enabled and were verified through the admin CLI before deployment approval
  • signing remains behind the protected armory-release reviewer gate
  • the workflow still requires the published release to report immutable == true
  • no key was read and no draft release was created by the failed run

Validation

  • actionlint v1.7.12
  • git diff --check
  • exact failed job and endpoint permission reviewed

@moloch--

Copy link
Copy Markdown
Author

Retriggering the pull_request event because GitHub did not create check suites for the initial opened event.

@moloch-- moloch-- closed this Aug 26, 2026
@moloch-- moloch-- reopened this Aug 26, 2026
@moloch--
moloch-- merged commit 19bec6f into main Aug 26, 2026
10 checks passed
@moloch--
moloch-- deleted the feat/immutable-preflight-fix branch August 26, 2026 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant