slack-machine
slack-machine copied to clipboard
chore(deps-dev): bump black from 23.9.1 to 24.2.0
Bumps black from 23.9.1 to 24.2.0.
Release notes
Sourced from black's releases.
24.2.0
Stable style
- Fixed a bug where comments where mistakenly removed along with redundant parentheses (#4218)
Preview style
- Move the
hug_parens_with_braces_and_square_brackets
feature to the unstable style due to an outstanding crash and proposed formatting tweaks (#4198)- Fixed a bug where base expressions caused inconsistent formatting of ** in tenary expression (#4154)
- Checking for newline before adding one on docstring that is almost at the line limit (#4185)
- Remove redundant parentheses in
case
statementif
guards (#4214).Configuration
- Fix issue where Black would ignore input files in the presence of symlinks (#4222)
- Black now ignores
pyproject.toml
that is missing atool.black
section when discovering project root and configuration. Since Black continues to use version control as an indicator of project root, this is expected to primarily change behavior for users in a monorepo setup (desirably). If you wish to preserve previous behavior, simply add an empty[tool.black]
to the previously discoveredpyproject.toml
(#4204)Output
- Black will swallow any
SyntaxWarning
s orDeprecationWarning
s produced by theast
module when performing equivalence checks (#4189)Integrations
- Add a JSONSchema and provide a validate-pyproject entry-point (#4181)
24.1.1
Bugfix release to fix a bug that made Black unusable on certain file systems with strict limits on path length.
Preview style
- Consistently add trailing comma on typed parameters (#4164)
Configuration
- Shorten the length of the name of the cache file to fix crashes on file systems that do not support long paths (#4176)
... (truncated)
Changelog
Sourced from black's changelog.
24.2.0
Stable style
- Fixed a bug where comments where mistakenly removed along with redundant parentheses (#4218)
Preview style
- Move the
hug_parens_with_braces_and_square_brackets
feature to the unstable style due to an outstanding crash and proposed formatting tweaks (#4198)- Fixed a bug where base expressions caused inconsistent formatting of ** in tenary expression (#4154)
- Checking for newline before adding one on docstring that is almost at the line limit (#4185)
- Remove redundant parentheses in
case
statementif
guards (#4214).Configuration
- Fix issue where Black would ignore input files in the presence of symlinks (#4222)
- Black now ignores
pyproject.toml
that is missing atool.black
section when discovering project root and configuration. Since Black continues to use version control as an indicator of project root, this is expected to primarily change behavior for users in a monorepo setup (desirably). If you wish to preserve previous behavior, simply add an empty[tool.black]
to the previously discoveredpyproject.toml
(#4204)Output
- Black will swallow any
SyntaxWarning
s orDeprecationWarning
s produced by theast
module when performing equivalence checks (#4189)Integrations
- Add a JSONSchema and provide a validate-pyproject entry-point (#4181)
24.1.1
Bugfix release to fix a bug that made Black unusable on certain file systems with strict limits on path length.
Preview style
- Consistently add trailing comma on typed parameters (#4164)
Configuration
- Shorten the length of the name of the cache file to fix crashes on file systems that do not support long paths (#4176)
... (truncated)
Commits
6fdf8a4
Prepare release 24.2.0 (#4226)8af4394
fix: Don't remove comments along with parens (#4218)35e9776
Bump pre-commit/action from 3.0.0 to 3.0.1 (#4225)23dfc5b
Fix ignoring input files for symlink reasons (#4222)a201003
Simplify check for symlinks that resolve outside root (#4221)dab37a6
Remove redundant parentheses incase
statementif
guards (#4214)32230e6
fix: bug where the doublestar operation had inconsistent formatting. (#4154)7edb50f
fix: additional newline added to docstring when the previous line length is l...3e80de3
Bump furo from 2023.9.10 to 2024.1.29 in /docs (#4211)a08b480
Bump pypa/cibuildwheel from 2.16.4 to 2.16.5 (#4212)- 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)
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
bf1112b
) 74.86% compared to head (3b3bf9a
) 74.86%.
Additional details and impacted files
@@ Coverage Diff @@
## main #982 +/- ##
=======================================
Coverage 74.86% 74.86%
=======================================
Files 27 27
Lines 1341 1341
=======================================
Hits 1004 1004
Misses 337 337
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Superseded by #993.