Bump pylint to 2.13.0, update changelog

Create the release summary upgrade the release process.

Bump pylint to 2.13.0, update changelog

ChangeLog

@@ -2,12 +2,29 @@
 Pylint's ChangeLog
 ------------------
 
-What's New in Pylint 2.13.0?
+What's New in Pylint 2.14.0?
 ============================
 Release date: TBA
 
 ..
-  Put new features here and also in 'doc/whatsnew/2.13.rst'
+  Put new features here and also in 'doc/whatsnew/2.14.rst'
+
+
+
+..
+  Insert your changelog randomly, it will reduce merge conflicts
+  (Ie. not necessarily at the end)
+
+
+What's New in Pylint 2.13.1?
+============================
+Release date: TBA
+
+
+
+What's New in Pylint 2.13.0?
+============================
+Release date: 2022-03-24
 
 * Add missing dunder methods to ``unexpected-special-method-signature`` check.
 
@@ -518,10 +535,6 @@ Release date: TBA
 
   Closes #214
 
-..
-  Insert your changelog randomly, it will reduce merge conflicts
-  (Ie. not necessarily at the end)
-
 * Improve ``invalid-name`` check for ``TypeVar`` names.
   The accepted pattern can be customized with ``--typevar-rgx``.
 
@@ -531,6 +544,14 @@ Release date: TBA
   or contravariant ``TypeVar`` does not end with  ``_co`` or ``_contra`` respectively or
   when a ``TypeVar`` is not either but has a suffix.
 
+* Allow usage of mccabe 0.7.x release
+
+  Closes #5878
+
+* Fix ``unused-private-member`` false positive when accessing private methods through ``property``.
+
+  Closes #4756
+
 
 What's New in Pylint 2.12.2?
 ============================
@@ -577,10 +598,6 @@ Release date: 2021-11-25
 
   Closes #5316
 
-* Allow usage of mccabe 0.7.x release
-
-  Closes #5878
-
 
 What's New in Pylint 2.12.1?
 ============================
@@ -609,10 +626,6 @@ Release date: 2021-11-24
 
   Closes #4412 #5287
 
-* Fix ``unused-private-member`` false positive when accessing private methods through ``property``.
-
-  Closes #4756
-
 * Fix ``install graphiz`` message which isn't needed for puml output format.
 
 * ``MessageTest`` of the unittest ``testutil`` now requires the ``confidence`` attribute

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.

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
 ============
 

pylint/__pkginfo__.py

@@ -4,7 +4,7 @@
 
 from typing import Tuple
 
-__version__ = "2.13.0-dev0"
+__version__ = "2.13.0"
 
 
 def get_numversion_from_version(v: str) -> Tuple:

tbump.toml

@@ -1,7 +1,7 @@
 github_url = "https://github.com/PyCQA/pylint"
 
 [version]
-current = "2.13.0-dev0"
+current = "2.13.0"
 regex = '''
 ^(?P<major>0|[1-9]\d*)
 \.