chore(deps): bump virtualenv from 21.7.5 to 21.7.7

[dependabot]

Bumps virtualenv from 21.7.5 to 21.7.7.

Release notes

Sourced from virtualenv's releases.

21.7.7

What's Changed

• 📄 docs: document the interpreter names in an environment by @​gaborbernat in pypa/virtualenv#3225
• 🎨 refactor(create): read the system exe without narrowing by @​gaborbernat in pypa/virtualenv#3224

Full Changelog: pypa/virtualenv@21.7.6...21.7.7

21.7.6

What's Changed

• 🐛 fix(create): name Windows venv exes after the interpreter by @​darrenhuai in pypa/virtualenv#3223

Full Changelog: pypa/virtualenv@21.7.5...21.7.6

Changelog

Sourced from virtualenv's changelog.

Bugfixes - 21.7.7

• Bump the python-discovery minimum to >=1.6 for PythonInfo.system_exe, which reports the system interpreter without the nullable typing of system_executable - by :user:gaborbernat. (:issue:3224)

Improved Documentation - 21.7.7

• Document the names the interpreter answers to inside a created environment. A new :doc:reference/environment-layout page lists them per platform, the tutorial and the usage guide point at it, and the explanation of creators covers why an environment carries several names and why Windows copies a redirector - by :user:gaborbernat. (:issue:3225)

---

v21.7.6 (2026-08-28)

---

Bugfixes - 21.7.6

• On Windows, virtualenv no longer copies the CPython 3.13+ venvlauncher.exe shim into Scripts under the shim's own name, and a host such as python_d.exe gets its alias back. The alias set took its names from the shim that stands in for the interpreter, so every environment gained a stray launcher copy and lost the interpreter's own file name - by :user:darrenhuai. (:issue:3223)

---

v21.7.5 (2026-08-25)

---

Commits

• b65d93d release 21.7.7
• 72776f2 🎨 refactor(create): read the system exe without narrowing (#3224)
• 8fab8d6 📄 docs: document the interpreter names in an environment (#3225)
• 267f4cd release 21.7.6
• 28c4cd1 🐛 fix(create): name Windows venv exes after the interpreter (#3223)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[amrit110]

Automated fix applied and PR merged

The agentic fix loop successfully fixed this PR and merged it.

✓ Successfully fixed merge_only failures - Modified 0 files - Executed 55 agent actions - (23 info, 16 tool_call, 1 error, 13 tool_result, 2 reasoning)

View PR history on dashboard

AI Engineering Maintenance Bot