What changed, and why it matters
This commit is a routine maintenance update to the project's automated build and test system. It upgrades the version of a commonly used GitHub-provided action (actions/checkout) from version 4 to version 5 in the project's CI workflow file. There is no indication of a security fix or vulnerability being addressed in the code itself.
No security action required. Treat as routine CI maintenance. Review the actions/checkout v5 release notes for any breaking changes if desired, but the change appears to be a straightforward version bump.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change modifies .github/workflows/main.yml, replacing all occurrences of ‘actions/checkout@v4’ with ‘actions/checkout@v5’. This is a standard dependency/version bump for the GitHub Actions checkout action used across CI jobs. The diff shows no functional changes to application code, no permission changes, no input changes, and no security-related configuration changes.
Changed components
.github/workflows/main.ymlInspect captured patch +14 / −14
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 7c4868d..cf0e39c 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -48,7 +48,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
# Needed for some checks.
fetch-depth: 0
@@ -115,7 +115,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -143,7 +143,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -179,7 +179,7 @@ jobs:
sys: darwin-arm64 freebsd-arm linux-armv6 linux-armv7 linux-arm64 windows-arm
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
- name: Clean up runner space
uses: ./.github/actions/cleanup-space
@@ -216,7 +216,7 @@ jobs:
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -228,7 +228,7 @@ jobs:
uses: ./.github/actions/rebase
- name: Git checkout fuzzing seeds
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
repository: lightninglabs/lnd-fuzz
path: lnd-fuzz
@@ -285,7 +285,7 @@ jobs:
args: backend=neutrino cover=1
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -365,7 +365,7 @@ jobs:
args: backend=bitcoind dbbackend=postgres nativesql=true tags=test_native_sql
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -425,7 +425,7 @@ jobs:
if: '!contains(github.event.pull_request.labels.*.name, ''no-itest'')'
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -469,7 +469,7 @@ jobs:
if: '!contains(github.event.pull_request.labels.*.name, ''no-itest'')'
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
with:
fetch-depth: 0
@@ -515,7 +515,7 @@ jobs:
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
- name: Clean up runner space
uses: ./.github/actions/cleanup-space
@@ -532,7 +532,7 @@ jobs:
if: '!contains(github.event.pull_request.labels.*.name, ''no-changelog'')'
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
- name: Clean up runner space
uses: ./.github/actions/cleanup-space
@@ -548,7 +548,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Git checkout
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
- name: 🐳 Set up Docker Buildx
uses: docker/setup-buildx-action@v3
@@ -569,7 +569,7 @@ jobs:
steps:
- name: Checkout repository
- uses: actions/checkout@v4
+ uses: actions/checkout@v5
- name: Delete caches older than 12 hours
continue-on-error: true
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.