chore(deps): bump h11 from 0.14.0 to 0.16.0

[dependabot]

Bumps h11 from 0.14.0 to 0.16.0.

Commits

• 1c5b075 this time for surer
• d9c3699 this time for sure...
• d91b9dd blacken
• 5a4683c Soothe mypy
• 9c9567f Bump version to 0.16.0
• 114803a Merge commit from fork
• 9462006 Bump version to 0.15.0
• 70a96be Merge pull request #181 from Julien00859/Julien00859/get_int_max_str_digits
• 60782ad Reject Content-Length longer 1 billion TB
• dff7cc3 Validate Chunked-Encoding chunk footer
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Important

Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

[Aaron ("AJ") Steers (aaronsteers)]

/poetry-lock

Poetry-Lock Job Info

This job attempts to re-lock dependencies using poetry lock command. If any changes
are made, those changes will be automatically committed and pushed back to the PR.

Note: This job can only be run by maintainers. On PRs from forks, this command requires
that the PR author has enabled the Allow edits from maintainers option.

poetry lock job started... Check job output.

✅ poetry lock applied successfully.

[Aaron ("AJ") Steers (aaronsteers)]

Documenting for future ref:

1. Dependabot is using a different version of Poetry, which causes a needlessly large and hard to read diff on the poetry.lock file: d70061d
2. By default, it looks like our downstream connector tests fail on Dependabot PRs - GitHub complains it doesn't have a github token.
3. Using the PR button to update from main apparently resolves # 2.
4. Running /poetry-lock resolves # 1, while not canceling the version bump. See all the noise reverted in 8e17ae1, and cleaner diff now on the PR.
5. Running /poetry-lock also seems to resolve # 1, since it adds a new commit from a non-Dependabot source (which apparently gets a good github token).

[David Gold (dbgold17)]

Documenting for future ref:

1. Dependabot is using a different version of Poetry, which causes a needlessly large and hard to read diff on the poetry.lock file: d70061d
2. By default, it looks like our downstream connector tests fail on Dependabot PRs - GitHub complains it doesn't have a github token.
3. Using the PR button to update from main apparently resolves # 2.
4. Running /poetry-lock resolves # 1, while not canceling the version bump. See all the noise reverted in 8e17ae1, and cleaner diff now on the PR.
5. Running /poetry-lock also seems to resolve # 1, since it adds a new commit from a non-Dependabot source (which apparently gets a good github token).

ok good to know. just clarifying, you meant to say "Running /poetry-lock also seems to resolve # 2,"? This tracks with the stuff you recently figured out around maintainer manually invoked workflows on forked community PRs.