-
Notifications
You must be signed in to change notification settings - Fork 918
Pin drivers-evergreen-tools to rev 98f6b0e in v1. #2184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin drivers-evergreen-tools to rev 98f6b0e in v1. #2184
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR pins the drivers-evergreen-tools repository to a specific revision (98f6b0e from Aug 20, 2025) to prevent build failures caused by breaking changes in the orchestration scripts as the v1/release/1.17 branches become more stale.
- Removes conditional logic for handling the "drivers-tools" project
- Adds explicit checkout of revision 98f6b0e after cloning drivers-evergreen-tools
- Includes explanatory comment about the pinning rationale
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
API Change ReportNo changes found! |
@matthewdale Following this up with https://jira.mongodb.org/browse/GODRIVER-3654 |
* release/1.17: GODRIVER-3612 Add an internal-only NewSessionWithLSID API (v1) (#2183) Consider HTTP 429 a succcessful response in the Markdown link check. (#2191) Pin drivers-evergreen-tools to rev 98f6b0e in v1. (#2184) Retry Markdown link checks on HTTP 429 (v1) (#2186)
Summary
Pin drivers-evergreen-tools to rev 98f6b0e in v1.
Background & Motivation
As the
v1
/release/1.17
branches continue to get more stale, the probability of breaking changes in the orchestration scripts increases. Pin the drivers-evergreen-tools repo to a version from Aug 20, 2025.Fixes build failures in #2183.