fix(ci): replace JS-based Renovate action with direct container invocation #73
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sarman/tftsr-devops_investigation#73
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/renovate-no-node-runner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The runner environment does not have Node.js in PATH, causing
actions/checkout@v4 and renovatebot/github-action@v41.0.0 (both JS
actions) to fail at startup.
Use renovate/renovate:latest as the job container and invoke the
renovate binary directly via run:, consistent with how all other
workflows in this repo handle checkout and tooling. The Checkout step
was also unnecessary — Renovate manages its own git operations.
Automated PR Review (qwen3-coder-next via liteLLM):\n\nSummary
The PR replaces a JS-based Renovate GitHub Action with direct invocation of the official Renovate container image. The updated workflow runs Renovate directly inside a container without requiring Node.js setup or JS-based actions, improving simplicity and maintainability. No issues affecting correctness, security, or functionality were identified.
Findings
renovate/renovate:latestmay lead to unpredictable behavior due to lack of pinning.Evidence:
image: renovate/renovate:latestFix: Pin to a specific tag (e.g.,
renovate/renovate:39.188.3) for reproducibility and stability.Verdict: APPROVE WITH COMMENTS