Fix stale workflow failure by updating actions/stale reference#33
Fix stale workflow failure by updating actions/stale reference#33SharkyBytes merged 1 commit intoAOSSIE-Org:mainfrom
Conversation
github-actions
bot
added
bug
WalkthroughUpdated the GitHub Actions stale workflow to reference Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/stale.yml:
- Line 18: Replace the mutable tag reference "uses: actions/stale@v10" with the
exact commit SHA to pin the action for reproducibility and security; update the
workflow line that currently references actions/stale@v10 to use the provided
commit SHA (b5d41d4e1d5dceea10e7104786b73624c18a190f) so the "uses:
actions/stale" entry is anchored to that specific commit.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 958c6f9f-93d9-402e-a6cc-1ecf27d8d50e
📒 Files selected for processing (1)
.github/workflows/stale.yml
| steps: | ||
| - name: Mark stale issues and PRs | ||
| uses: actions/stale@9d5a0b4d7a0d8b4f2c5e7d5b8a6c2a3f7a2b1c9d | ||
| uses: actions/stale@v10 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
ref_json="$(curl -fsSL https://api.github.com/repos/actions/stale/git/ref/tags/v10)"
obj_type="$(jq -r '.object.type' <<<"$ref_json")"
obj_sha="$(jq -r '.object.sha' <<<"$ref_json")"
if [ "$obj_type" = "tag" ]; then
commit_sha="$(curl -fsSL "https://api.github.com/repos/actions/stale/git/tags/$obj_sha" | jq -r '.object.sha')"
else
commit_sha="$obj_sha"
fi
echo "Resolved actions/stale@v10 commit SHA: $commit_sha"
echo "Update .github/workflows/stale.yml to:"
echo "uses: actions/stale@$commit_sha"Repository: AOSSIE-Org/SmartNotes
Length of output: 244
🏁 Script executed:
cat -n .github/workflows/stale.yml | sed -n '15,25p'Repository: AOSSIE-Org/SmartNotes
Length of output: 387
Pin actions/stale to a commit SHA instead of the mutable tag v10.
Using the major version tag @v10 on line 18 allows the reference to be retargeted, introducing supply chain risk. Pin to the exact commit SHA for reproducibility and security.
The v10 release resolves to commit b5d41d4e1d5dceea10e7104786b73624c18a190f. Update the workflow:
Suggested change
- uses: actions/stale@v10
+ uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| uses: actions/stale@v10 | |
| uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/workflows/stale.yml at line 18, Replace the mutable tag reference
"uses: actions/stale@v10" with the exact commit SHA to pin the action for
reproducibility and security; update the workflow line that currently references
actions/stale@v10 to use the provided commit SHA
(b5d41d4e1d5dceea10e7104786b73624c18a190f) so the "uses: actions/stale" entry is
anchored to that specific commit.
|
Oh, this was actually needed! This was failing continuously. LGTM |
Fix stale workflow failure by updating actions/stale reference
2 participants
Closes #32
📝 Description
This fixes the stale workflow failure caused by an invalid actions/stale reference that could not be downloaded from GitHub.
The workflow now uses a valid and maintained action version, so scheduled and manual stale runs can execute successfully.
🔧 Changes Made
-> Updated the stale GitHub Action reference from a broken pinned SHA to actions/stale@v10.
-> Kept existing stale behavior unchanged:
days-before-stale: 30
days-before-close: 7
-> stale labels/messages for issues and PRs remain the same.
No functional logic changes beyond resolving the action download failure.
📷 Screenshots or Visual Changes (if applicable)
🤝 Collaboration
Collaborated with:
@username(optional)✅ Checklist
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.
Summary by CodeRabbit