Skip to content

Revise workflows based on correct security standards - #511

Merged
poespas merged 4 commits into
masterfrom
revise-workflows-standards
Jul 28, 2026
Merged

Revise workflows based on correct security standards#511
poespas merged 4 commits into
masterfrom
revise-workflows-standards

Conversation

@poespas

@poespas poespas commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Jonathan Visser added 3 commits July 28, 2026 13:32
pull_request_target runs are not gated by the fork approval policy and
carry a write token, so installing requirements from the pull request
head let any fork execute arbitrary code in a privileged context. Check
out the base branch for pip install first; the head is only checked out
afterwards and processed as data by mdformat.
hypernode-deploy's prepare:ssh task hard-fails when the ssh-agent has no
identities (it lists loaded keys unconditionally), so builds without
SSH_PRIVATE_KEY cannot pass even though building needs no server access.
Generate a key that grants access to nothing instead of reintroducing
the real deploy key into jobs that run untrusted pull request code.
@github-actions

Copy link
Copy Markdown
Contributor

Acceptance server is available at https://docs-ephx9045w.hypernode.io.

@poespas
poespas merged commit 7875120 into master Jul 28, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants