renovate/lib/modules/manager/github-actions
HonkingGoose c6824223aa
docs: update references to Ubuntu versions (#28701)
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
2024-04-29 15:14:21 +00:00
..
__fixtures__ feat(github-actions): add support for version tag prefixes (#27882) 2024-03-13 19:11:16 +00:00
__snapshots__ feat(manager/github-actions): extract complex github tags (#27941) 2024-03-26 14:41:47 +00:00
extract.spec.ts feat(manager/github-actions): extract complex github tags (#27941) 2024-03-26 14:41:47 +00:00
extract.ts feat(manager/github-actions): extract complex github tags (#27941) 2024-03-26 14:41:47 +00:00
index.ts feat(manager/github-actions): support full qualified actions (#27117) 2024-02-08 07:59:28 +00:00
readme.md docs: update references to Ubuntu versions (#28701) 2024-04-29 15:14:21 +00:00
types.ts feat(github-actions): support GitHub actions runners (#23633) 2023-08-08 19:59:41 +00:00

readme.md

The github-actions manager extracts dependencies from GitHub Actions workflow and workflow template files. It can also be used for Gitea and Forgejo Actions workflows as such are compatible with GitHub Actions workflows.

If you like to use digest pinning but want to follow the action version tag, you can use the sample below:

name: build

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@3df4ab11eba7bda6032a0b82a6bb43b11571feac # v4.0.0

Renovate will update the commit SHA according to the GitHub tag you specified. Renovate can update digests that use SHA1 and SHA256 algorithms. The GitHub tag is in the format of (prefix-)(v)1.0.0, where prefix and v are optional and 1.0.0 is the version number. Here are the examples of valid GitHub tags: 1.0.1, 1.0, 1, v1.0.1, v1.0, v1, prefix-1.0.1, prefix-1.0, prefix-1, prefix-v1.0.1, prefix-v1.0, prefix-v1.

If you want to automatically pin action digests add the helpers:pinGitHubActionDigests preset to the extends array:

{
  "extends": ["helpers:pinGitHubActionDigests"]
}

Renovate ignores any GitHub runners which are configured in variables. For example, Renovate ignores the runner configured in the RUNNER variable:

name: build
on: [push]

env:
  RUNNER: ubuntu-22.04

jobs:
  build:
    runs-on: ${{ env.RUNNER }}

The github-action manager understands ratchet comments, like # ratchet:actions/checkout@v2.1.0. This means that Renovate will:

  • update the version of a pinned Ratchet version if needed
  • not delete Ratchet comments after parsing them
  • keep # ratchet:exclude comments