Latest Results
[PR #14121/44334f11 backport][3.14] bump flake8 plugins on pre-commit (#14123)
**This is a backport of PR #14121 as merged into master
(44334f115485596829dd5abd1a84efce4f5e274e).**
<!-- Thank you for your contribution! -->
## What do these changes do?
Bump flake8 plugin deps on pre-commit to latest versions. Currently
yesqa is failing on precommit on
https://results.pre-commit.ci/run/github/13258039/1792932051.JYaFwCOwRz2NadODrJIBbg
, It looks like the old version of flake8-requirements it's having
compatibility issues
<!-- Please give a short brief about these changes. -->
## Are there changes in behavior for the user?
No, the change is only on CI
<!-- Outline any notable behaviour for the end users. -->
## Is it a substantial burden for the maintainers to support this?
No
<!--
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
- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] 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`.
```
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.
Co-authored-by: Pablo Nicolás Estevez <pablo22estevez@gmail.com> [PR #14121/44334f11 backport][3.15] bump flake8 plugins on pre-commit (#14122)
**This is a backport of PR #14121 as merged into master
(44334f115485596829dd5abd1a84efce4f5e274e).**
<!-- Thank you for your contribution! -->
## What do these changes do?
Bump flake8 plugin deps on pre-commit to latest versions. Currently
yesqa is failing on precommit on
https://results.pre-commit.ci/run/github/13258039/1792932051.JYaFwCOwRz2NadODrJIBbg
, It looks like the old version of flake8-requirements it's having
compatibility issues
<!-- Please give a short brief about these changes. -->
## Are there changes in behavior for the user?
No, the change is only on CI
<!-- Outline any notable behaviour for the end users. -->
## Is it a substantial burden for the maintainers to support this?
No
<!--
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
- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] 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`.
```
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.
Co-authored-by: Pablo Nicolás Estevez <pablo22estevez@gmail.com> bump flake8 plugins on pre-commit (#14121)
<!-- Thank you for your contribution! -->
## What do these changes do?
Bump flake8 plugin deps on pre-commit to latest versions. Currently
yesqa is failing on precommit on
https://results.pre-commit.ci/run/github/13258039/1792932051.JYaFwCOwRz2NadODrJIBbg
, It looks like the old version of flake8-requirements it's having
compatibility issues
<!-- Please give a short brief about these changes. -->
## Are there changes in behavior for the user?
No, the change is only on CI
<!-- Outline any notable behaviour for the end users. -->
## Is it a substantial burden for the maintainers to support this?
No
<!--
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
- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] 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`.
```
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 44334f115485596829dd5abd1a84efce4f5e274e)patchback/backports/3.15/44334f115485596829dd5abd1a84efce4f5e274e/pr-14121 bump flake8 plugins on pre-commit (#14121)
<!-- Thank you for your contribution! -->
## What do these changes do?
Bump flake8 plugin deps on pre-commit to latest versions. Currently
yesqa is failing on precommit on
https://results.pre-commit.ci/run/github/13258039/1792932051.JYaFwCOwRz2NadODrJIBbg
, It looks like the old version of flake8-requirements it's having
compatibility issues
<!-- Please give a short brief about these changes. -->
## Are there changes in behavior for the user?
No, the change is only on CI
<!-- Outline any notable behaviour for the end users. -->
## Is it a substantial burden for the maintainers to support this?
No
<!--
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
- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] 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`.
```
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. bump flake8 plugins on pre-commit (#14121)
<!-- Thank you for your contribution! -->
## What do these changes do?
Bump flake8 plugin deps on pre-commit to latest versions. Currently
yesqa is failing on precommit on
https://results.pre-commit.ci/run/github/13258039/1792932051.JYaFwCOwRz2NadODrJIBbg
, It looks like the old version of flake8-requirements it's having
compatibility issues
<!-- Please give a short brief about these changes. -->
## Are there changes in behavior for the user?
No, the change is only on CI
<!-- Outline any notable behaviour for the end users. -->
## Is it a substantial burden for the maintainers to support this?
No
<!--
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
- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] 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`.
```
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 44334f115485596829dd5abd1a84efce4f5e274e)patchback/backports/3.14/44334f115485596829dd5abd1a84efce4f5e274e/pr-14121 Latest Branches
0%
Polandia94:modernized-issues-and-pull-request-templates 0%
patchback/backports/3.15/44334f115485596829dd5abd1a84efce4f5e274e/pr-14121 0%
patchback/backports/3.14/44334f115485596829dd5abd1a84efce4f5e274e/pr-14121 © 2026 CodSpeed Technology