diff options
author | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2022-03-24 15:42:23 +0100 |
---|---|---|
committer | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2022-03-24 23:13:17 +0100 |
commit | fd0eb6c2af0e3e98350e24047c4df7d5b8aad89a (patch) | |
tree | da1a13070bf6bbae32fad2501e8afd956dc6f25f /doc | |
parent | 1c509edc4ee2dbf1bbe8822e91e0b7df02ce463d (diff) | |
download | pylint-git-fd0eb6c2af0e3e98350e24047c4df7d5b8aad89a.tar.gz |
Bump pylint to 2.13.0, update changelogv2.13.0
Create the release summary upgrade the release process.
Bump pylint to 2.13.0, update changelog
Diffstat (limited to 'doc')
-rw-r--r-- | doc/release.md | 3 | ||||
-rw-r--r-- | doc/whatsnew/2.13.rst | 20 |
2 files changed, 21 insertions, 2 deletions
diff --git a/doc/release.md b/doc/release.md index 25c87bbe5..07b4a647b 100644 --- a/doc/release.md +++ b/doc/release.md @@ -8,6 +8,8 @@ So, you want to release the `X.Y.Z` version of pylint ? the maintenance branch. If so, release a last patch release first. See `Releasing a patch version`.** +- Write the `Summary -- Release highlights` in `doc/whatsnew` and upgrade the release + date. - Remove the empty changelog for the last unreleased patch version `X.Y-1.Z'`. (For example: `v2.3.5`) - Check the result of `git diff vX.Y-1.Z' ChangeLog`. (For example: @@ -36,7 +38,6 @@ Check the commit, fixup the 'wip' commit with the what's new then push to a rele branch - Open a merge request with the two commits (no one can push directly on `main`) -- Trigger the "release tests" workflow in GitHub Actions. - After the merge, recover the merged commits on `main` and tag the first one (the version should be `X.Y.Z`) as `vX.Y.Z` (For example: `v2.4.0`) - Push the tag. diff --git a/doc/whatsnew/2.13.rst b/doc/whatsnew/2.13.rst index c03335247..7b209042e 100644 --- a/doc/whatsnew/2.13.rst +++ b/doc/whatsnew/2.13.rst @@ -3,11 +3,29 @@ *************************** :Release: 2.13 -:Date: TBA +:Date: 2022-03-24 Summary -- Release highlights ============================= +In 2.13, we introduced a new check to deal with unicode security issues. On top of that a lot of work was +done inside the unicode checker by @CarliJoy. We also introduced a new check when importing private name +and for unnecessary ellipsis among other. + +We fixed long standing issues related to duplicate code that could not be disabled, line numbers +that were not accurate some of the time, and added the ability to lint all files in a directory without +specifying each one. One of the most anticipated issue from the repository. Thank you @matusvalo ! + +A lot of ``undefined-variables`` and ``used-before-assignment`` issues were resolved thanks to @jacobtylerwalls. + +We started integrating ``pylint-error`` the documentation created by @vald-phoenix a developer from Hlyniane, +Ukraine. We hope he's doing well despite the current situation. The deployment is set up but `there's still a lot to do so we welcome any community effort +help to review, integrate, and add good/bad examples <https://github.com/PyCQA/pylint/issues/5953>`_. This should be doable +without any pylint or astroid knowledge, so this is the perfect entrypoint if you want to contribute +to pylint without investing any time learning the internals. + +This release is the last one to support interpreter below 3.7.2, 3.6 end of life was reached in december 2021. + New checkers ============ |