Bump pylint to 2.13.1, update changelog

CONTRIBUTORS.txt

@@ -121,6 +121,7 @@ contributors:
 - David Gilman <[email protected]>
 - Andrew Haigh <[email protected]> (nelfin)
 - へーさん <[email protected]>
+- orSolocate <[email protected]>
 - Thomas Hisch <[email protected]>
 - Marianna Polatoglou <[email protected]>: minor contribution for wildcard import check
 - Manuel Vázquez Acosta <[email protected]>
@@ -138,7 +139,6 @@ contributors:
   * Added new extension which detects comparing integers to zero,
   * Added new useless-return checker,
   * Added new try-except-raise checker
-- orSolocate <[email protected]>
 - Téo Bouvard <[email protected]>
 - Tushar Sadhwani <[email protected]> (tusharsadhwani)
 - Mihai Balint <[email protected]>

ChangeLog

@@ -10,15 +10,22 @@ Release date: TBA
   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?
+What's New in Pylint 2.13.2?
 ============================
 Release date: TBA
 
+
+
+What's New in Pylint 2.13.1?
+============================
+Release date: 2022-03-26
+
 * Fix a regression in 2.13.0 where ``used-before-assignment`` was emitted for
   the usage of a nonlocal in a try block.
 

doc/release.md

@@ -45,6 +45,8 @@ branch
   appropriate changelog in the description. This triggers the PyPI release.
 - Delete the `maintenance/X.Y-1.x` branch. (For example: `maintenance/2.3.x`)
 - Create a `maintenance/X.Y.x` (For example: `maintenance/2.4.x` from the `v2.4.0` tag.)
+- Close the current milestone and create the new ones (For example: close `2.4.0`,
+  create `2.4.1` and `2.6.0`)
 
 ## Backporting a fix from `main` to the maintenance branch
 
@@ -67,8 +69,7 @@ cherry-picked on the maintenance branch.
 - Install the release dependencies: `pip3 install -r requirements_test.txt`
 - Bump the version and release by using `tbump X.Y-1.Z --no-push`. (For example:
   `tbump 2.3.5 --no-push`)
-- Check the result visually and then by triggering the "release tests" workflow in
-  GitHub Actions first.
+- Check the result visually with `git show`.
 - Push the tag.
 - Release the version on GitHub with the same name as the tag and copy and paste the
   appropriate changelog in the description. This triggers the PyPI release.
@@ -77,6 +78,8 @@ cherry-picked on the maintenance branch.
   `pre-commit autoupdate` works for pylint.
 - Fix version conflicts properly, or bump the version to `X.Y.0-devZ` (For example:
   `2.4.0-dev6`) before pushing on the main branch
+- Close the current milestone and create the new one (For example: close `2.3.5`, create
+  `2.3.6`)
 
 ## Milestone handling
 

pylint/__pkginfo__.py

@@ -4,7 +4,7 @@
 
 from typing import Tuple
 
-__version__ = "2.13.0"
+__version__ = "2.13.1"
 
 
 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"
+current = "2.13.1"
 regex = '''
 ^(?P<major>0|[1-9]\d*)
 \.