Skip to content

ci(security): add dd-octo-sts policy for Node.js base image publishing#6957

Draft
rochdev wants to merge 1 commit into
mainfrom
rochdev/nodejs-base-images-publish-policy
Draft

ci(security): add dd-octo-sts policy for Node.js base image publishing#6957
rochdev wants to merge 1 commit into
mainfrom
rochdev/nodejs-base-images-publish-policy

Conversation

@rochdev
Copy link
Copy Markdown
Member

@rochdev rochdev commented May 17, 2026

Summary

Adds a dd-octo-sts policy that restricts GHCR package writes to pushes on main via the dedicated publish-nodejs-base-images reusable workflow.

This is a prerequisite for #6903, which will switch from using GITHUB_TOKEN with packages: write to using a scoped dd-octo-sts token — preventing PR branches from pushing arbitrary image tags.

The claim is not wired up in #6903 yet; this policy just needs to be merged first so the token can be requested once #6903 is ready to switch over.

🤖 Generated with Claude Code

Restricts GHCR package writes to pushes on main via the dedicated
publish-nodejs-base-images reusable workflow only.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

CODEOWNERS have been resolved as:

.github/chainguard/self.publish-nodejs-base-images.sts.yaml             @DataDog/system-tests-core

rochdev added a commit that referenced this pull request May 17, 2026
Moves the GHCR push logic to publish-nodejs-base-images.yml so it can
later be protected with a dd-octo-sts claim (see PR #6957) to restrict
pushes to main-branch runs only.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
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