Release branch 3.0.0a7

[Pierre-Sassoulas]

No description provided.

[codecov]

Codecov Report

Merging #2242 (a29effd) into main (e91a3b5) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2242   +/-   ##
=======================================
  Coverage   92.77%   92.77%           
=======================================
  Files          94       94           
  Lines       10941    10941           
=======================================
  Hits        10151    10151           
  Misses        790      790           

Flag	Coverage Δ
linux	92.58% <100.00%> (ø)
pypy	90.89% <100.00%> (ø)
windows	92.34% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
astroid/__pkginfo__.py	100.00% <100.00%> (ø)

[jacobtylerwalls]

In #1867 (review) I was hoping not to merge the Try node changes until we had 3.0.0a7 released, but now that the Try node changes are merged in, we have two large pylint PRs to do at the same time.

I'm okay with merging this as is, but in terms of doing the pylint upgrades, should we just keep the two PRs separate, and have the first one pin to a specific commit since we don't have another separate alpha for it?

[Pierre-Sassoulas]

We could also cheat/rewrite the history or merge a branch install in pylint ?

[jacobtylerwalls]

or merge a branch install in pylint

I'll just pin to the hotfix commit on the existing pylint upgrade PR and that pin will only be there for a day or two on main until we do the Try node update PR, and it won't be a problem.

Thanks!