Latest Results
Removed old issue template (#13791)
<!-- Thank you for your contribution! -->
Remove old issue_template.md file, as the project currently uses
issue_template directory
<!-- Please give a short brief about these changes. -->
No, this issue template was not accesible when creating an issue
<!-- Outline any notable behaviour for the end users. -->
No, this should just remove an unused file
<!--
Stop right there! Pause. Just for a minute... Can you think of anything
obvious that would complicate the ongoing development of this project?
Try to consider if you'd be able to maintain it throughout the next
5 years. Does it seem viable? Tell us your thoughts! We'd very much
love to hear what the consequences of merging this patch might be...
This will help us assess if your change is something we'd want to
entertain early in the review process. Thank you in advance!
-->
<!-- Will this resolve any open issues? -->
<!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes
- [ ] I think the code is well written N/A
- [ ] Unit tests for the changes exist N/A
- [ ] Documentation reflects the changes
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
* The format is <Name> <Surname>.
* Please keep alphabetical order, the file is sorted by names.
- [ ] Add a new news fragment into the `CHANGES/` folder
* name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`)
* if you don't have an issue number, change it to the pull request
number after creating the PR
* `.bugfix`: A bug fix for something the maintainers deemed an
improper undesired behavior that got corrected to match
pre-agreed expectations.
* `.feature`: A new behavior, public APIs. That sort of stuff.
* `.deprecation`: A declaration of future API removals and breaking
changes in behavior.
* `.breaking`: When something public is removed in a breaking way.
Could be deprecated in an earlier release.
* `.doc`: Notable updates to the documentation structure or build
process.
* `.packaging`: Notes for downstreams about unobvious side effects
and tooling. Changes in the test invocation considerations and
runtime assumptions.
* `.contrib`: Stuff that affects the contributor experience. e.g.
Running tests, building the docs, setting up the development
environment.
* `.misc`: Changes that are hard to assign to any of the above
categories.
* Make sure to use full sentences with correct case and punctuation,
for example:
```rst
Fixed issue with non-ascii contents in doctest text files
-- by :user:`contributor-gh-handle`.
```
I think this doesn't require a changes file, ut happy to add it
Use the past tense or the present tense a non-imperative mood,
referring to what's changed compared to the last released version
of this project.
(cherry picked from commit 7e67714dc2efbe3ed72199841801957873ad8e59)Polandia94:patchback/backports/3.14/7e67714dc2efbe3ed72199841801957873ad8e59/pr-13791 Removed old issue template (#13791)
<!-- Thank you for your contribution! -->
Remove old issue_template.md file, as the project currently uses
issue_template directory
<!-- Please give a short brief about these changes. -->
No, this issue template was not accesible when creating an issue
<!-- Outline any notable behaviour for the end users. -->
No, this should just remove an unused file
<!--
Stop right there! Pause. Just for a minute... Can you think of anything
obvious that would complicate the ongoing development of this project?
Try to consider if you'd be able to maintain it throughout the next
5 years. Does it seem viable? Tell us your thoughts! We'd very much
love to hear what the consequences of merging this patch might be...
This will help us assess if your change is something we'd want to
entertain early in the review process. Thank you in advance!
-->
<!-- Will this resolve any open issues? -->
<!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes
- [ ] I think the code is well written N/A
- [ ] Unit tests for the changes exist N/A
- [ ] Documentation reflects the changes
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
* The format is <Name> <Surname>.
* Please keep alphabetical order, the file is sorted by names.
- [ ] Add a new news fragment into the `CHANGES/` folder
* name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`)
* if you don't have an issue number, change it to the pull request
number after creating the PR
* `.bugfix`: A bug fix for something the maintainers deemed an
improper undesired behavior that got corrected to match
pre-agreed expectations.
* `.feature`: A new behavior, public APIs. That sort of stuff.
* `.deprecation`: A declaration of future API removals and breaking
changes in behavior.
* `.breaking`: When something public is removed in a breaking way.
Could be deprecated in an earlier release.
* `.doc`: Notable updates to the documentation structure or build
process.
* `.packaging`: Notes for downstreams about unobvious side effects
and tooling. Changes in the test invocation considerations and
runtime assumptions.
* `.contrib`: Stuff that affects the contributor experience. e.g.
Running tests, building the docs, setting up the development
environment.
* `.misc`: Changes that are hard to assign to any of the above
categories.
* Make sure to use full sentences with correct case and punctuation,
for example:
```rst
Fixed issue with non-ascii contents in doctest text files
-- by :user:`contributor-gh-handle`.
```
I think this doesn't require a changes file, ut happy to add it
Use the past tense or the present tense a non-imperative mood,
referring to what's changed compared to the last released version
of this project.
(cherry picked from commit 7e67714dc2efbe3ed72199841801957873ad8e59)Polandia94:patchback/backports/3.15/7e67714dc2efbe3ed72199841801957873ad8e59/pr-13791 Fix CI failures: mypy, spelling wordlist, test assertion
Pin truststore in requirements/lint.in and lint.txt, same as
aiofastnet, so mypy actually resolves it instead of erroring with
"Cannot find implementation". Once resolved, truststore's own type
stubs make its module-level name a concrete ModuleType, so the
except-branch fallback needs an explicit `ModuleType | None`
annotation rather than a bare type: ignore comment, and the
SSLContext returned by truststore.SSLContext() needs a cast since
mypy can't otherwise tell it matches the ssl.SSLContext alias this
function returns.
Added the three new technical terms (certifi, stdlib, truststore) to
docs/spelling_wordlist.txt, sphinxcontrib-spelling flagged all three
with warnings-as-errors on.
Removed a redundant assertion in
test_verified_ssl_context_falls_back_without_truststore: asserting
an ssl.SSLContext instance is not NoneType is trivially true and
mypy correctly flags the isinstance check itself as unreachable.ishan-1010:feat/truststore-ssl-verification Removed old issue template (#13791)
<!-- Thank you for your contribution! -->
## What do these changes do?
Remove old issue_template.md file, as the project currently uses
issue_template directory
<!-- Please give a short brief about these changes. -->
## Are there changes in behavior for the user?
No, this issue template was not accesible when creating an issue
<!-- Outline any notable behaviour for the end users. -->
## Is it a substantial burden for the maintainers to support this?
No, this should just remove an unused file
<!--
Stop right there! Pause. Just for a minute... Can you think of anything
obvious that would complicate the ongoing development of this project?
Try to consider if you'd be able to maintain it throughout the next
5 years. Does it seem viable? Tell us your thoughts! We'd very much
love to hear what the consequences of merging this patch might be...
This will help us assess if your change is something we'd want to
entertain early in the review process. Thank you in advance!
-->
## Related issue number
<!-- Will this resolve any open issues? -->
<!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes
#123'). -->
## Checklist
- [ ] I think the code is well written N/A
- [ ] Unit tests for the changes exist N/A
- [ ] Documentation reflects the changes
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
* The format is <Name> <Surname>.
* Please keep alphabetical order, the file is sorted by names.
- [ ] Add a new news fragment into the `CHANGES/` folder
* name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`)
* if you don't have an issue number, change it to the pull request
number after creating the PR
* `.bugfix`: A bug fix for something the maintainers deemed an
improper undesired behavior that got corrected to match
pre-agreed expectations.
* `.feature`: A new behavior, public APIs. That sort of stuff.
* `.deprecation`: A declaration of future API removals and breaking
changes in behavior.
* `.breaking`: When something public is removed in a breaking way.
Could be deprecated in an earlier release.
* `.doc`: Notable updates to the documentation structure or build
process.
* `.packaging`: Notes for downstreams about unobvious side effects
and tooling. Changes in the test invocation considerations and
runtime assumptions.
* `.contrib`: Stuff that affects the contributor experience. e.g.
Running tests, building the docs, setting up the development
environment.
* `.misc`: Changes that are hard to assign to any of the above
categories.
* Make sure to use full sentences with correct case and punctuation,
for example:
```rst
Fixed issue with non-ascii contents in doctest text files
-- by :user:`contributor-gh-handle`.
```
I think this doesn't require a changes file, ut happy to add it
Use the past tense or the present tense a non-imperative mood,
referring to what's changed compared to the last released version
of this project. Latest Branches
0%
Polandia94:patchback/backports/3.14/7e67714dc2efbe3ed72199841801957873ad8e59/pr-13791 +9%
Polandia94:patchback/backports/3.15/7e67714dc2efbe3ed72199841801957873ad8e59/pr-13791 +9%
dependabot/github_actions/3.15/astral-sh/setup-uv-10.2.0 Ā© 2026 CodSpeed Technology