ci: remove fetch-tags from checkout
What changed, and why it matters
This commit removes some GitHub Actions checkout settings that were causing the automated release workflow to fail. It is a CI/CD pipeline fix with no security relevance to the Core Lightning software itself or its users.
No security action needed. Treat as a normal CI maintenance commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch removes fetch-depth: 0 and fetch-tags: true from three actions/checkout@v4 steps in .github/workflows/release.yml. The commit message explains these options caused a Git fetch conflict when the release action tried to fetch both a commit and a tag pointing to the same ref. This is a workflow reliability fix, not a code or cryptographic change.
Changed components
.github/workflows/release.ymlInspect captured patch +0 / −6
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index f7a92bd3..3021efe4 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -31,8 +31,6 @@ jobs:
uses: actions/checkout@v4
with:
ref: ${{ github.ref }}
- fetch-depth: 0
- fetch-tags: true
- name: Determine version
run: |
@@ -69,8 +67,6 @@ jobs:
steps:
- name: Git checkout
uses: actions/checkout@v4
- with:
- fetch-tags: true
# tools/build-release.sh requires lowdown
- name: Prepare base environment
@@ -129,8 +125,6 @@ jobs:
steps:
- name: Git checkout
uses: actions/checkout@v4
- with:
- fetch-tags: true
- name: Download artifact
uses: actions/download-artifact@v4
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.