Skip to content

Mutable tags break linting of GitHub Actions workflows #37

Description

@iainsproat

On July 16th 2026 the v1.0.0-beta tag was moved from commit 41cdeedae8edb2e684ba22896a5fd2a3cb85db6b to 01ab2a058dd0d41e292217b76582a6f9867c02ce.

For security reasons we pin the versions of checkout to the commit SHA and note the expected version number in a trailing comment, as follows:

    steps:
      - name: Checkout repository
        uses: useblacksmith/checkout@41cdeedae8edb2e684ba22896a5fd2a3cb85db6b # v1.0.0-beta
        with:
          persist-credentials: false

Tooling, such as Zizmor, are able to lint this to ensure the documented version matches the commit sha. If mutable tags are used, our downstream pipelines break.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions