[setuptools] Force the upgrade of setuptools > 77

[Pierre-Sassoulas]

Type of Changes

	Type
✓	🔨 Refactoring

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.21%. Comparing base (cf64a90) to head (ad1b0a8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2715   +/-   ##
=======================================
  Coverage   93.21%   93.21%           
=======================================
  Files          93       93           
  Lines       11071    11071           
=======================================
  Hits        10320    10320           
  Misses        751      751           

Flag	Coverage Δ
linux	93.08% <ø> (ø)
pypy	93.21% <ø> (ø)
windows	93.19% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

The backport to maintenance/3.3.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-maintenance/3.3.x maintenance/3.3.x
# Navigate to the new working tree
cd .worktrees/backport-maintenance/3.3.x
# Create a new branch
git switch --create backport-2715-to-maintenance/3.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9a2d66a398160b5fb73742371883e57d054a3330
# Push it to GitHub
git push --set-upstream origin backport-2715-to-maintenance/3.3.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-maintenance/3.3.x

Then, create a pull request where the base branch is maintenance/3.3.x and the compare/head branch is backport-2715-to-maintenance/3.3.x.

[cdce8p]

It seems we didn't backport two previous PRs this one relied on:

• [pre-commit.ci] pre-commit autoupdate #2681
• Update coverage requirement from ~=7.6 to ~=7.7 #2707

Not sure if it's worth it at this point to do the backport manually. The bug which was fixed here won't happen on the backport branch since that hasn't adopted PEP 639 yet. What do you think @Pierre-Sassoulas ?

[Pierre-Sassoulas]

I'm going to do it as we might want to release a lot of patch version before astroid 4.0.0 is out