Skip to content

Security policy and Dependabot for GitHub Actions - #1

Merged
teo1747 merged 1 commit into
mainfrom
chore/security-policy-dependabot
Nov 11, 2026
Merged

teo1747 merged 1 commit into
mainfrom
chore/security-policy-dependabot

Conversation

@teo1747

@teo1747 teo1747 commented Nov 11, 2026

Copy link
Copy Markdown
Member

What

  • SECURITY.md: how to report a vulnerability privately (GitHub's private vulnerability reporting, now on), what to include, and what happens next.
  • .github/dependabot.yml: one grouped pull request a week when an action used by CI has a new version. The core has no runtime dependencies yet, so no pip entry.
  • ci.yml: the DCO check skips commits authored by dependabot[bot], which cannot sign off. Those pull requests still need every other check to pass.

Why

The repository is public now. People need a private way to report security problems, and CI's actions should not go stale.

This is also the first change through the new main ruleset: a pull request with all 11 checks passing.

SECURITY.md asks for vulnerabilities to be reported privately
through GitHub's private vulnerability reporting, now switched on,
and says what to include and what happens next.

Dependabot opens one grouped pull request a week when an action
used by CI has a new version. Dependabot cannot sign off its
commits, so the DCO check skips commits authored by dependabot[bot];
they are still reviewed and must pass every other check.

Signed-off-by: teo1747 <148846371+teo1747@users.noreply.github.com>
@teo1747
teo1747 merged commit 121e84a into main Nov 11, 2026
11 checks passed
@teo1747
teo1747 deleted the chore/security-policy-dependabot branch November 11, 2026 17:49
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