From 552baf822992936134cbd31a38f69c8cfe7c0f05 Mon Sep 17 00:00:00 2001 From: Jelle Zijlstra Date: Fri, 15 Mar 2024 12:17:00 -0700 Subject: [PATCH] Prepare release 24.3.0 (#4279) --- CHANGES.md | 38 ++------------------- docs/integrations/source_version_control.md | 4 +-- docs/usage_and_configuration/the_basics.md | 6 ++-- 3 files changed, 7 insertions(+), 41 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index ffd24feb31c..a1d674d5b5b 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -1,11 +1,9 @@ # Change Log -## Unreleased +## 24.3.0 ### Highlights - - This release is a milestone: it fixes Black's first CVE security vulnerability. If you run Black on untrusted input, or if you habitually put thousands of leading tab characters in your docstrings, you are strongly encouraged to upgrade immediately to fix @@ -16,32 +14,14 @@ incorrect changes to certain f-strings that are valid in Python 3.12 and higher. ### Stable style - - - Don't move comments along with delimiters, which could cause crashes (#4248) - Strengthen AST safety check to catch more unsafe changes to strings. Previous versions of Black would incorrectly format the contents of certain unusual f-strings containing nested strings with the same quote type. Now, Black will crash on such strings until support for the new f-string syntax is implemented. (#4270) -- Fixed a bug where line-ranges exceeding the last code line would not work as expected +- Fix a bug where line-ranges exceeding the last code line would not work as expected (#4273) -### Preview style - - - -### Configuration - - - -### Packaging - - - -### Parser - - - ### Performance - Fix catastrophic performance on docstrings that contain large numbers of leading tab @@ -49,23 +29,9 @@ incorrect changes to certain f-strings that are valid in Python 3.12 and higher. [CVE-2024-21503](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21503). (#4278) -### Output - - - -### _Blackd_ - - - -### Integrations - - - ### Documentation - Note what happens when `--check` is used with `--quiet` (#4236) - ## 24.2.0 diff --git a/docs/integrations/source_version_control.md b/docs/integrations/source_version_control.md index f24043026fa..541debdc556 100644 --- a/docs/integrations/source_version_control.md +++ b/docs/integrations/source_version_control.md @@ -8,7 +8,7 @@ Use [pre-commit](https://pre-commit.com/). Once you repos: # Using this mirror lets us use mypyc-compiled black, which is about 2x faster - repo: https://github.com/psf/black-pre-commit-mirror - rev: 24.2.0 + rev: 24.3.0 hooks: - id: black # It is recommended to specify the latest version of Python @@ -35,7 +35,7 @@ include Jupyter Notebooks. To use this hook, simply replace the hook's `id: blac repos: # Using this mirror lets us use mypyc-compiled black, which is about 2x faster - repo: https://github.com/psf/black-pre-commit-mirror - rev: 24.2.0 + rev: 24.3.0 hooks: - id: black-jupyter # It is recommended to specify the latest version of Python diff --git a/docs/usage_and_configuration/the_basics.md b/docs/usage_and_configuration/the_basics.md index 7aa8a644bea..9ce72823850 100644 --- a/docs/usage_and_configuration/the_basics.md +++ b/docs/usage_and_configuration/the_basics.md @@ -269,8 +269,8 @@ configuration file for consistent results across environments. ```console $ black --version -black, 24.2.0 (compiled: yes) -$ black --required-version 24.2.0 -c "format = 'this'" +black, 24.3.0 (compiled: yes) +$ black --required-version 24.3.0 -c "format = 'this'" format = "this" $ black --required-version 31.5b2 -c "still = 'beta?!'" Oh no! 💥 💔 💥 The required version does not match the running version! @@ -366,7 +366,7 @@ You can check the version of _Black_ you have installed using the `--version` fl ```console $ black --version -black, 24.2.0 +black, 24.3.0 ``` #### `--config`