Skip to content

CI: read-only default token, exact build/twine in publish jobs - #83

Merged
wardviaene merged 1 commit into
mainfrom
supply-chain-ci
Nov 14, 2026
Merged

wardviaene merged 1 commit into
mainfrom
supply-chain-ci

Conversation

@wardviaene

Copy link
Copy Markdown
Member

L18 of the 2026-11 security review (embeddedci-python part).

  • ci.yml: top-level permissions: contents: read (it had none, so it ran with the repo default token). publish.yml calls it as a reusable workflow; tests only read the repo.
  • publish.yml: the build steps run in jobs that hold id-token: write for trusted publishing and installed the latest build and twine. They now install build==1.6.1 and twine==7.0.0.

CI-only.

🤖 Generated with Claude Code

L18 of the 2026-11 security review: ci.yml had no top-level permissions, so it ran with the
repository default token. It now declares contents: read. The publish jobs (id-token: write for
trusted publishing) installed the latest build and twine; they now install exact versions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wardviaene
wardviaene merged commit 5663dbd into main Nov 14, 2026
20 checks passed
@wardviaene
wardviaene deleted the supply-chain-ci branch November 14, 2026 23:38
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