Bump pyinstaller from 6.21.0 to 6.22.2 in /python in the development group across 1 directory

[dependabot]

Bumps the development group with 1 update in the /python directory: pyinstaller.

Updates pyinstaller from 6.21.0 to 6.22.2

Release notes

Sourced from pyinstaller's releases.

v6.22.2

Please see the v6.22.2 section of the changelog for a list of the changes since v6.22.1.

v6.22.1

Please see the v6.22.1 section of the changelog for a list of the changes since v6.22.0.

v6.22.0

Please see the v6.22.0 section of the changelog for a list of the changes since v6.21.0.

Changelog

Sourced from pyinstaller's changelog.

6.22.2 (2026-08-17)

Bugfix

* (Windows) Fix spurious security validation error when a ``onefile``
  executable is launched from a symlinked directory or a junction.
  (:issue:`9508`)
6.22.1 (2026-08-15)
Bugfix

• Fix invalid spec file generation when :option:--hide-console option is given (regression introduced in v6.22.0). (:issue:9503)
• (NetBSD) Fix binary dependency analysis. (:issue:9505)
• (NetBSD) Fix/improve NetBSD support: add the is_netbsd platform flag, treat NetBSD as a Unix platform, and search /usr/local/lib for shared libraries, as is already done for FreeBSD and OpenBSD. (:issue:9496)
• (OpenBSD) Fix binary dependency analysis. (:issue:9505)

Incompatible Changes

* (POSIX) Executables built in ``onedir`` mode with ``setuid`` bit set
  now validate the owner and permissions on their contents directory
  (typically the ``_internal`` directory); the owner ID must match the
  effective user ID under which the process is running, and the
  permissions on the directory need to be `0700`. This aims to prevent
  unprivileged users from modifying contents of an application that
  runs in privileged mode. (:issue:`9492`)
* (POSIX) When running as a ``onefile`` child process (on POSIX platforms
  other than OpenBSD and AIX), the bootloader now attempts to verify
  the parent process executable via ``procfs`` lookup. This check is
  mandatory for ``onefile`` executables with ``setuid`` bit set; if the
  relevant ``procfs`` entry is inaccessible (for example, due to ``procfs``
  not being mounted, as is the case on FreeBSD by default, or due to access
  being blocked by local security policy), the process will exit with
  security validation error message. For regular ``onefile`` executables
  (without ``setuid`` bit set), the parent-process check is enforced when the
  relevant ``procfs`` entry is accessible, and skipped when it happens to be
  inaccessible. (:issue:`9492`)
* (POSIX) When running as a ``onefile`` child process and the executable
  has ``setuid`` bit set, the bootloader now validates the owner and
  permissions on the (inherited) temporary directory. The owner ID of the
</tr></table> 

... (truncated)

Commits

• 19f42e7 Release v6.22.2. [skip ci]
• 72bbdb4 bootloader: Windows: use QueryFullProcessImageNameW for executable resolution
• 0d6941c tests: add test to ensure security validation works with symlinked executables
• 6e00368 Tests: Requirements: Scheduled weekly dependency update for week 33 (#9506)
• 22ea0f2 Release v6.22.1. [skip ci]
• e709c04 bootloader: relax parent-process validation requirements on POSIX platforms
• e0388d3 bootloader: relax parent-process validation requirements on FreeBSD
• 92afdf8 tests: test_application_home_directory_hijack: handle 8.3 short paths
• 4b509a2 tests: improve logging in test_application_home_directory_hijack
• 66b0249 doc: document the new security validation and its implications
• Additional commits viewable in compare view

[aleksandrychev]

@dependabot rebase