Skip to content

ci: read-only token by default; fork PRs never on the self-hosted runner - #102

Merged
vu1n merged 1 commit into
mainfrom
claude/project-thread-b36guq
Nov 13, 2026
Merged

vu1n merged 1 commit into
mainfrom
claude/project-thread-b36guq

Conversation

@vu1n

@vu1n vu1n commented Nov 13, 2026

Copy link
Copy Markdown
Owner

Requested by Vu · project thread

Hardening after the wfx credential-theft campaign.

  • python.yml, worker.yml and release.yml declare permissions: contents: read at the top. release.yml's deploy job still grants itself contents: write and id-token: write. This way, setting the repo default to read-only breaks nothing.
  • python.yml picks the netcup self-hosted runner when vars.RUNNER_LABEL is set. A fork PR would then run its code on our host. Fork PRs now always use ubuntu-latest.

Not a worker change, so it deploys nothing. YAML parses. CI on this PR exercises both workflows.


Generated by Claude Code

Each workflow now declares contents: read, so none depends on the repo's default token permissions.
python.yml could run a fork's PR on the netcup runner when RUNNER_LABEL is set; it now uses a hosted one.
@vu1n
vu1n merged commit 52444f0 into main Nov 13, 2026
4 checks passed
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