Merge release/1.17 into release/2.2

[mongodb-drivers-pr-bot]

Merge new changes from release/1.17 into release/2.2.

Commits

• Pin drivers-evergreen-tools to rev 98f6b0e in v1. (Pin drivers-evergreen-tools to rev 98f6b0e in v1. #2184): 8c336ff
• Retry Markdown link checks on HTTP 429 (v1) (Retry Markdown link checks on HTTP 429 (v1) #2186): 106cff3

Resolving conflicts

To resolve any conflicts, check out the temporary branch and run the following command:

git merge release/2.2

Ignoring changes

To ignore from the remote branch, first reset the temporary branch to release/2.2 and manually merge using the `ours` merge strategy:

git reset --hard release/2.2
git merge --strategy=ours release/1.17

Then, push the temporary branch to upate the pull request.

[mongodb-drivers-pr-bot]

API Change Report

No changes found!

[prestonvasquez]

The yml language server removed these empty spaces while resolving conflicts.

[prestonvasquez]

@matthewdale This solution doesn't appear to always resolve the blogspot HTTP 429 issue. markdown-lint-check has a specific retryOn429 option that they recommend using. From the related docs:

retryOn429: if this is true then retry request when response is an HTTP code 429 after the duration indicated by retry-after header.

This will require giving the hook a config file .markdown-link-check-config.json:

{
	"retryOn429": true,
	"retryCount": 5,
	"fallbackRetryDelay": "60s"
}

- id: markdown-link-check
  exclude: ^(vendor)
  # Retry when the endpoint returns HTTP 429 (Too Many Requests)
  args: ["-c", ".markdown-link-check-config.json"]

[evergreen-ci-prod]

There is an existing patch(es) for this commit SHA:

• Evergreen patch with PR

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

[prestonvasquez]

@matthewdale This PR was automatically closed after ignoring changes:

git reset --hard release/2.2
git merge --strategy=ours release/1.17

We are ignoring the changes since the -r is flakey (opting for an ignore-429s solution) and we don't want to pin DET for 2.x branches.