⬆️ Update pyinstaller requirement from ~=6.18.0 to ~=6.22.3

[dependabot]

Updates the requirements on pyinstaller to permit the latest version.

Release notes

Sourced from pyinstaller's releases.

v6.22.3

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

Changelog

Sourced from pyinstaller's changelog.

6.22.3 (2026-09-12)

Bugfix

* (Windows) Revise earlier fix for :issue:`9508` to avoid breaking
  executables located on ImDisk RAMDISK volumes. (:issue:`9510`)
* Compare the icon file suffix case-insensitively, so an icon named with an
  upper-case suffix such as ``MyApp.ICO`` is recognised as already being in the
  right format instead of being rejected or silently re-encoded.
  (:issue:`9521`)
* Fix ``onefile`` parent-process validation to allow intermixed nested
  sub-processes. (:issue:`9513`)
Bootloader

• (POSIX) Enable onefile parent-process validation for POSIX executables that have setgid bit set, and for Linux executables that have file capabilities set (i.e., have a security.capability extended file attribute). (:issue:9524)
• (POSIX) Revise the validation of owner and permissions of onedir application's contents directory when the executable has either setuid or setgid bit set. If setuid bit is set, the owner ID of the application's contents directory must match the owner ID of the executable itself, and only owner is allowed to have write permissions on the directory. If setgid bit is set, the group ID of the application's contents directory must match the group ID of the executable itself, and only owner and the group are allowed to have write permissions on the directory. (:issue:9524)
• Limit onefile parent-process validation only to executables that are running with elevated privileges while inheriting environment variables set by unprivileged user. On POSIX systems, this corresponds to executables with setuid bit set, while on Windows, it corresponds to UAC-elevated processes (running with TokenElevationTypeFull token). (:issue:9520)

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`)
</tr></table>

... (truncated)

Commits

• ecd7993 Release v6.22.3. [skip ci]
• 8807296 doc: update documentation section on onefile/onedir security verification
• bda6110 bootloader: security: improve owner/permissions check in onedir mode
• e3fc240 bootloader: security: add detection of file capabilities on linux
• 3d73d32 bootloader: security: enable security checks for setgid executables
• 10c62c5 bootloader: security: make early-error message a bit more generic
• 1919af1 Tests: Requirements: Scheduled weekly dependency update for week 36 (#9522)
• 77907b5 doc: update documentation section on onefile security verification
• a36324b ci: freebsd: mount /proc
• 012e150 tests: security: adjust for platforms without parent-process verification
• Additional commits viewable 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.