Bump pyinstaller from 6.1.0 to 6.2.0 (#6519)

Bumps [pyinstaller](https://github.com/pyinstaller/pyinstaller) from
6.1.0 to 6.2.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pyinstaller/pyinstaller/releases">pyinstaller's
releases</a>.</em></p>
<blockquote>
<h2>v6.2.0</h2>
<p>Please see the <a
href="https://pyinstaller.org/en/v6.2.0/CHANGES.html#id1">v6.2.0 section
of the changelog</a> for a list of the changes since v6.1.0.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/pyinstaller/pyinstaller/blob/develop/doc/CHANGES.rst">pyinstaller's
changelog</a>.</em></p>
<blockquote>
<h2>6.2.0 (2023-11-11)</h2>
<p>Features</p>
<pre><code>
* (macOS) At the end of analysis, verify the macOS SDK version reported
by binaries to be collected, and warn when the version is either invalid
(0.0.0) or too low (&lt; 10.9.0). Such binaries will likely cause issues
  with code-signing and hardened runtime. (:issue:`8043`)
* If the ``argcomplete`` Python module is installed, PyInstaller will
use it
enable tab completion for its CLI tools. PyInstaller CLIs can still be
used
  without this optional dependency. To install ``argcomplete`` with
PyInstaller, you can put ``pyinstaller[completion]`` in your
dependencies.
  See also `the argcomplete documentation
  &lt;https://kislyuk.github.io/argcomplete/&gt;`_. (:issue:`8008`)
<p>Bugfix</p>
<pre><code>
* (macOS) Fix the bug in binary processing and caching that would update
  the binary cache index before performing macOS-specific processing
(architecture validation, path rewriting). If, for example, architecture
  validation failed during a build, subsequent build attempts with
enabled binary cache (i.e., without the :option:`--clean` option) would
pick up the partially-processed binary file from the cache, bypassing
the
  architecture validation. NOTE: the existing binary caches need to be
purged manually (using :option:`--clean` option once) for the fix to
take
  effect! (:issue:`8068`)
* (macOS) Prevent collection of ``.DS_Store`` files, which might be
present
in build environment's package directories after user navigated them
using
  the Finder app. (:issue:`8042`)
* (Windows) Fix marshal error at the start of binary dependency
analysis,
  caused by inferred DLL search path ending up an instance of
  :class:`pathlib.Path` instead of :class:`str`. (:issue:`8081`)
* Bump the required ``packaging`` version to 22.0, which is required for
  proper handling of metadata that contains markers with ``extra``\ s.
  (:issue:`8061`)
* Fix erroneous DLL parent path preservation when
:data:`sys.base_prefix`
  itself is a symbolic link. In such case, we need to exclude both
resolved and unresolved path variant for ``sys.base_prefix``, in order
to
  prevent either from ending up in the list of directories for which DLL
  parent paths are preserved. Failing to do so, for example, caused
  ``_ctypes`` failing to load in an application build on Windows with
Python installed via ``scoop``, due to ``libffi-8.dll`` having
spuriously
preserved the parent directory path instead of being collected to
top-level
  application directory. (:issue:`8023`)
* Fix matching of pre-release versions in
  :func:`PyInstaller.utils.hooks.check_requirement` and
&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt; 
&lt;/code&gt;&lt;/pre&gt;
&lt;/blockquote&gt;
&lt;p&gt;... (truncated)&lt;/p&gt;
&lt;/details&gt;
&lt;details&gt;
&lt;summary&gt;Commits&lt;/summary&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a
href=&quot;90c9ac4231&quot;&gt;&lt;code&gt;90c9ac4&lt;/code&gt;&lt;/a&gt;
Release v6.2.0. [skip ci]&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;ae525ceffe&quot;&gt;&lt;code&gt;ae525ce&lt;/code&gt;&lt;/a&gt;
hookutils: fix pre-release matching in check_requirement /
is_module_satisfies&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;13de1077d5&quot;&gt;&lt;code&gt;13de107&lt;/code&gt;&lt;/a&gt;
building: fix marshal error during DLL search path extension&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;04db9fdaea&quot;&gt;&lt;code&gt;04db9fd&lt;/code&gt;&lt;/a&gt;
rth_utils: add is_macos_app_bundle flag&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;1e0e551ea9&quot;&gt;&lt;code&gt;1e0e551&lt;/code&gt;&lt;/a&gt;
rth_utils: remove relative import work-around&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;ecc218ceb5&quot;&gt;&lt;code&gt;ecc218c&lt;/code&gt;&lt;/a&gt;
analysis: fix module exclusion for relative imports from
submodules&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;03627c2b2b&quot;&gt;&lt;code&gt;03627c2&lt;/code&gt;&lt;/a&gt;
tests: add test for exclusion of relatively-imported modules&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;e157bb6c16&quot;&gt;&lt;code&gt;e157bb6&lt;/code&gt;&lt;/a&gt;
hooks: add a hook for our _pyi_rth_utils fake package&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;574a961917&quot;&gt;&lt;code&gt;574a961&lt;/code&gt;&lt;/a&gt;
rth_utils: move secure_mkdtemp() implementation to a
submodule&lt;/li&gt;
&lt;li&gt;&lt;a
href=&quot;983bd59dc6&quot;&gt;&lt;code&gt;983bd59&lt;/code&gt;&lt;/a&gt;
rthooks: pkg_resources: normalize path using os.path.normpath&lt;/li&gt;
&lt;li&gt;Additional commits viewable in &lt;a
href=&quot;https://github.com/pyinstaller/pyinstaller/compare/v6.1.0...v6.2.0&quot;&gt;compare
view&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/details&gt;

&lt;br /&gt;
</code></pre>


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyinstaller&package-manager=pip&previous-version=6.1.0&new-version=6.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@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)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

pyproject.toml

@@ -65,7 +65,7 @@ dev = [
     "click>=7.0,<8.2",
     "hypothesis>=5.8,<7",
     "pdoc>=4.0.0",
-    "pyinstaller==6.1.0",
+    "pyinstaller==6.2.0",
     "pytest-asyncio>=0.17,<0.22",
     "pytest-cov>=2.7.1,<4.2",
     "pytest-timeout>=1.3.3,<2.3",