Skip to content

Qualify GitHub Actions v7 dependency upgrades #442

Description

@leehack

Scope

Track and qualify the three open Dependabot major-version upgrades:

Required validation

  • Integrate current main normally and do not force-push.
  • Review upstream release and migration notes for breaking input, permission, runtime, artifact, and token behavior.
  • Preserve least-privilege permissions and existing provenance, coverage, artifact-retention, checkout-depth, submodule, and credential contracts.
  • Merge sequentially so each subsequent PR is refreshed and revalidated on current main.
  • Require exact-head CI, zero unresolved review threads, and independent blocking-only QA before mark-ready.
  • Verify post-merge workflows after each accepted upgrade.

Acceptance criteria

  • Each upgrade is either merged with exact-current-main evidence or closed with a documented compatibility reason.
  • No workflow permission, artifact, provenance, coverage, or checkout regression is introduced.
  • Existing action versions remain acceptable for the next release, so this issue is not itself release-blocking unless upstream security or compatibility evidence changes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency fileenhancementNew feature or requestgithub_actionsPull requests that update GitHub Actions codepriority:P3Watch or strategic work blocked by upstream/runtime/design dependencies

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions