fix(build): increase release-please search depths to prevent 250-commit window issue #342
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…it window issue - add release-search-depth (800) and commit-search-depth (1000) at root level - add explicit include-component-in-tag setting to match existing tag format 🔧 - Generated by Copilot
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #342 +/- ##
==========================================
- Coverage 52.46% 52.43% -0.04%
==========================================
Files 17 17
Lines 3084 3084
==========================================
- Hits 1618 1617 -1
- Misses 1466 1467 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a release-please configuration issue where the tool fails to detect version tags beyond its default ~250 commit scanning window, causing it to incorrectly reprocess the entire commit history and detect already-released breaking changes.
Changes:
- Added search depth configurations (
release-search-depth: 800,commit-search-depth: 1000) to expand release-please's commit scanning window - Added explicit tag format configuration (
include-component-in-tag: true) to match the existinghve-core-vX.Y.Ztag pattern
katriendg
approved these changes
Feb 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Configure release-please search depths to prevent version detection failures when the latest release tag is beyond the default commit scanning window. This addresses a known limitation (googleapis/release-please#2267) where release-please fails to find tags older than ~250 commits, causing it to reprocess the entire commit history and incorrectly detect already-released breaking changes.
release-search-depth: 800at root level to increase release pagination depthcommit-search-depth: 1000at root level to increase commit scanning depthinclude-component-in-tag: trueto explicitly match the existing tag format (hve-core-vX.Y.Z)Related Issue(s)
Related to googleapis/release-please#2267
Type of Change
Select all that apply:
Code & Documentation:
Infrastructure & Configuration:
AI Artifacts:
prompt-builderagent and addressed all feedback.github/instructions/*.instructions.md).github/prompts/*.prompt.md).github/agents/*.agent.md)Other:
.ps1,.sh,.py)Sample Prompts (for AI Artifact Contributions)
N/A - This is a configuration fix, not an AI artifact contribution.
Testing
node -e "require('./release-please-config.json')"Checklist
Required Checks
AI Artifact Contributions
N/A
Required Automated Checks
The following validation commands must pass before merging:
npm run lint:mdnpm run spell-checknpm run lint:frontmatternpm run lint:md-linksnpm run lint:psSecurity Considerations
Additional Notes
This fix addresses the erroneous v3.0.0 release PR (#341) that was created immediately after publishing v2.0.1. The root cause was the 250-commit window limitation causing release-please to reprocess the entire commit history and re-detect the breaking change from PR #277 that was already released in v2.0.0.
🔧 - Generated by Copilot