Renovate exits silently mid-run starting from 43.195.11 while processing terraform files #43639
-
How are you running Renovate?Self-hosted Renovate CLI Which platform you running Renovate on?GitHub.com Which version of Renovate are you using?43.195.11 is the first observed failing, 43.195.10 is the last observed working. Please tell us more about your question or problemSince 43.195.11, the Renovate GitHub Actions step exits cleanly but seems to stop part-way through - only 1 of our 4 configured repos is processed. No exception, no The last debug line in every failed run is from terraform-providers hash calculation: In good runs (before 43.195.11) the same line appears, hashes finish, processing continues. Reproduces under Setup (possibly relevant)Self-hosted runner; 4 private repos are configured to be proceesed by Renovate; first is a Terraform monorepo. Relevant workflow step (our repository is private): - name: Renovate
uses: renovatebot/github-action@693b9ef15eec82123529a37c782242f091365961 # v46.1.14
with:
renovate-image: "ghcr.io/renovatebot/renovate"
renovate-version: "43.195.11" # The first "bad" version
docker-user: root
configurationFile: "${{ env.RENOVATE_CONFIG_FILE }}"
token: "${{ steps.generate-token.outputs.token }}"
env-regex: "^(?:RENOVATE_\\w+|LOG_LEVEL|AWS_ACCESS_KEY_ID|AWS_SECRET_ACCESS_KEY|AWS_REGION|GHCR_PAT)$"
env:
GHCR_PAT: ${{ secrets.RENOVATE_GHCR_PAT }}
AWS_ACCESS_KEY_ID: ${{ secrets.RENOVATE_AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.RENOVATE_AWS_SECRET_ACCESS_KEY }}
AWS_REGION: ap-northeast-1Speculation (low confidence)Between 43.195.10 → 43.195.11 the only source change is Questions
Logs (if relevant)LogsBad run (43.195.11)(~2 s between the last Renovate line and Post-job cleanup. No further Renovate output; the Action step concluded Good run (43.195.10) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
|
Looking into it |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
🤗