Commit Graph
3 Commits
Author SHA1 Message Date
Aleksei Sviridkin 8aa30472b6 docs(ci): correct the job-level permissions comment
The comment above the top-level `permissions` block claimed that jobs
request the minimum extra scopes on top of it. A job-level block does
not add to the workflow-level one: it replaces it, and every scope the
job does not name is set to none. A job needing one extra scope has to
restate `contents: read` alongside it or lose read access to the
repository.

The corrected wording states the replace semantics, so the next job
block written against this comment grants the whole set it needs
rather than only the delta.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-08-07 00:34:53 +03:00
Myasnikov Daniil 76ad921fdd ci: harden workflow token permissions and pin actions by SHA
Raise the OpenSSF Scorecard Token-Permissions and Pinned-Dependencies
checks (both currently 0/10) ahead of CNCF Incubation due diligence:

- Declare a top-level read-only default (permissions: contents: read) in
  every workflow, plus an explicit per-job permissions: block that grants
  only the writes that job actually needs. Workflows that previously held
  write scopes at the workflow level (backport, pr-labeler, pr-size,
  stale) now hold them at job level instead.
- Pin every GitHub-owned and third-party action to a full commit SHA with
  a version comment. scorecard.yml was already pinned in #2721.

No triggers, job graph, or step logic change; only token scopes and
action refs. Self-hosted release jobs keep the exact write scopes they
already declared.

Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Assisted-By: Claude <noreply@anthropic.com>
2026-06-23 11:32:16 +05:00
Aleksei Sviridkin bc6d147b85 chore(ci): replace Dosu stale and size labeling with native workflows
Add two GitHub-native workflows ahead of disabling the Dosu app and
migrate size labels to canonical k8s namespacing.

- .github/workflows/stale.yaml uses actions/stale@v10 to manage the
  lifecycle/stale and lifecycle/rotten lifecycle. Daily cron, 60d
  before stale, 14d before close. Issue/PR exempt lists differ on
  purpose: an accepted issue (triage/accepted) is a known long-tail
  task, not stale; a held PR (do-not-merge/hold) is paused
  intentionally. Priority/security/regression labels protect issues
  someone explicitly decided to keep visible.

- .github/workflows/pr-size.yaml uses actions/github-script@v7 to
  apply size/* labels based on diff line count. Thresholds match the
  descriptions in .github/labels.yml. Inline ignore patterns skip
  vendored deps, kubebuilder/openapi inline generated files
  (zz_generated.{deepcopy,conversion,defaults,openapi}.go), whole
  code-generated trees (any path under generated/ or *.pb.go),
  vendored Helm charts, and lockfiles. Concurrency group keyed on PR
  number with cancel-in-progress: true. removeLabel is wrapped in
  try/catch tolerating 404 for races between event payload and
  execution.

- Migrate the six size labels from legacy 'size:X' (colon) to
  canonical 'size/X' (slash) via aliases in .github/labels.yml. The
  colon form was an artefact of the previous sizing bot's output;
  with the bot replaced and namespacing already used everywhere else
  (kind/, area/, priority/, triage/, lifecycle/, do-not-merge/,
  security/), the slash form aligns with the rest of the scheme. The
  alias migration preserves IDs and keeps every existing labelled PR
  pointing at the renamed entry.

  pr-size.yaml emits the new 'size/' form from day 1 and accepts
  either prefix when looking up the previous size label, to handle
  the brief window between PR merge and the labels-sync run.

Verification of zero hard dependencies on Dosu in workflows: only
backport.yaml (consumes backport*, applied by humans only) and
pull-requests*.yaml + tags.yaml (consume release, applied by tags
workflow itself) — none of those labels come from Dosu.

The lgtm label (33/33 in last 100 PRs from Dosu, none from humans)
is intentionally not replaced in this PR — observe reviewer
behaviour for 7 days after Dosu is disabled and decide whether a
pull_request_review-on-approve workflow is needed.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-04-27 18:00:01 +03:00