Repository navigation
ci: limit release-please commit search depth - #163
Conversation
release-please has been failing with a GraphQL error while fetching merge commits on main; cap the search depth.
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 1
✨ Finishing Touches
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #163 +/- ##
=======================================
Coverage 75.04% 75.04%
=======================================
Files 7 7
Lines 4577 4577
=======================================
Hits 3435 3435
Misses 1142 1142
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
🟡 Changes recommended
The configured limit reduces history scanning but does not reduce individual GraphQL query sizes as intended.
1 open issue
What changed in this PR
This PR aims to mitigate recurring release-please GraphQL failures by limiting commit-history scanning in the existing release workflow.
Changes:
- Sets
commit-search-depthto 50 in the release-please configuration.
| File | Description |
|---|---|
| release-please-config.json | Caps the number of commits searched during release preparation. |
Review effort: Balanced
| @@ -1,4 +1,5 @@ | |||
| { | |||
| "commit-search-depth": 50, | |||

release-please fails with a GitHub GraphQL error while fetching merge commits on main (three runs in a row). Cap commit-search-depth at 50 so the query is smaller.
Summary by CodeRabbit