Skip to content

chore(deps-dev): bump pyinstaller from 6.20.0 to 6.21.0#261

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/pyinstaller-6.21.0
Open

chore(deps-dev): bump pyinstaller from 6.20.0 to 6.21.0#261
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/pyinstaller-6.21.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 1, 2026

Copy link
Copy Markdown
Contributor

Bumps pyinstaller from 6.20.0 to 6.21.0.

Release notes

Sourced from pyinstaller's releases.

v6.21.0

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

Changelog

Sourced from pyinstaller's changelog.

6.21.0 (2026-06-13)

Features


* Add support for Python 3.15. (:issue:`9456`)
* Initial support for setting :ref:`alternative splash screen centering modes
  <splash screen centering>` for multi-monitor setups. (:issue:`6271`)

Hooks


* Prevent ``_ios_support`` and ``libobjc.so`` from being collected on non-IOS
  platforms if :mod:`webbrowser` is imported. (:issue:`9436`)
* Update ``scipy`` hook for compatibility with upcoming ``scipy`` v1.18.0.
  (:issue:`9450`)
* Update the ``gi.repository.Adw`` hook to collect translation files
  for ``libadwaita``. (:issue:`9444`)

Documentation
</code></pre>
<ul>
<li>Document known issues with using splash screen in <code>onedir</code> GUI-based
applications. (:issue:<code>9425</code>)</li>
<li>Document the &quot;glowing magenta border&quot; problem in splash screen when
splash screen image contains semi-transparent pixels (for example,
due to feathered edges). (:issue:<code>9425</code>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>

<ul>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/1cda34561015a90b6e1ae31dc89703799adaf13e&quot;&gt;&lt;code&gt;1cda345&lt;/code&gt;&lt;/a> Release v6.21.0. [skip ci]</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/14b6af36cd7284360e7094e66e97ddef76412876&quot;&gt;&lt;code&gt;14b6af3&lt;/code&gt;&lt;/a> tests: use different module in TestModuleGraph::test_find_module</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/6041ae39584fbb0606c1f936e33e656c075859a8&quot;&gt;&lt;code&gt;6041ae3&lt;/code&gt;&lt;/a> tests: modulegraph: skip tests that are incompatible with python 3.15</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/dd3c5601e58fa3b7993486d5bd9f769653f6ee24&quot;&gt;&lt;code&gt;dd3c560&lt;/code&gt;&lt;/a> tests: adjust bytecode sanity-check tests for python 3.15</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/08f4d82600302727dfc210ec38aa9eeebaf7a671&quot;&gt;&lt;code&gt;08f4d82&lt;/code&gt;&lt;/a> modulegraph: adapt _scan_bytecode() for changes in python 3.15</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/13c2e638918528e7b15b7f048aa01d6de9fe9b50&quot;&gt;&lt;code&gt;13c2e63&lt;/code&gt;&lt;/a> modulegraph: improve assert messages in _scan_bytecode()</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/d4fd4f442a214a656e4fc690f86e998d08d46bcb&quot;&gt;&lt;code&gt;d4fd4f4&lt;/code&gt;&lt;/a> depend: bytecode: add support for LOAD_COMMON_CONSTANT</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/5a9f21030ed91f7dc394a24c4e660c742ad6bf07&quot;&gt;&lt;code&gt;5a9f210&lt;/code&gt;&lt;/a> bootstrap: fix issues caused by encodings being frozen in python 3.15</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/8d97d35a2c04162be04a33748318308e09d398a4&quot;&gt;&lt;code&gt;8d97d35&lt;/code&gt;&lt;/a> tests: test_spec_options: explicitly disable argparse colored output</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/10d0772984f885246d002a7963c728c118639225&quot;&gt;&lt;code&gt;10d0772&lt;/code&gt;&lt;/a> tests: use can_import_module('tkinter') with all tkinter/splash tests</li>
<li>Additional commits viewable in <a href="https://github.com/pyinstaller/pyinstaller/compare/v6.20.0...v6.21.0&quot;&gt;compare view</a></li>
</ul>
</details>

<br />

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jul 1, 2026

@rtibblesbot rtibblesbot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependabot patch bump: pyinstaller 6.20.0 → 6.21.0 in the build dev-extras group (pyproject.toml).

  • Semver risk: patch. Dependency type: development (packaging/build tool only, not shipped in the app runtime).
  • Changelog: no breaking changes or security fixes — additive only (Python 3.15 support, splash-screen multi-monitor centering, scipy/gi.repository.Adw/webbrowser hook updates).
  • CI: failing on all three jobs (lint/uv-lock, Build Unsigned EXE, Build Unsigned DMG), all with the identical root cause — not a compatibility issue with the new pyinstaller release.

Blocking:

  • pyproject.toml:46 pins exclude-newer = "2026-06-03T00:00:00Z", which predates pyinstaller 6.21.0's publish date (2026-06-13). uv therefore refuses to resolve the bump ("No solution found... pyinstaller was filtered by exclude-newer"). This is maintainer-controlled housekeeping outside this PR's diff — Dependabot can't fix it. Someone needs to bump exclude-newer past 2026-06-13 in a separate change before this PR can pass CI, or this PR should stay closed until that happens.

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a dependency-update review pipeline over the version bump:

  • Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
  • Extracted the changelog and release notes across the version range
  • Assessed compatibility with this project's usage and whether any code changes are required
  • Treated CI as the primary safety net
  • Scaled the review depth to the update's risk
  • Chose the verdict from semver risk, changelog findings, and CI status

@rtibbles

rtibbles commented Jul 1, 2026

Copy link
Copy Markdown
Member

@dependabot rebase

Bumps [pyinstaller](https://github.com/pyinstaller/pyinstaller) from 6.20.0 to 6.21.0.
- [Release notes](https://github.com/pyinstaller/pyinstaller/releases)
- [Changelog](https://github.com/pyinstaller/pyinstaller/blob/develop/doc/CHANGES.rst)
- [Commits](pyinstaller/pyinstaller@v6.20.0...v6.21.0)

---
updated-dependencies:
- dependency-name: pyinstaller
  dependency-version: 6.21.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/pip/pyinstaller-6.21.0 branch from ea29620 to 82f51a5 Compare July 1, 2026 03:58

@rtibblesbot rtibblesbot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 of 1 prior findings resolved; 1 new blocking finding (see below).

Dependency update: pyinstaller 6.20.0 → 6.21.0 (dev dependency, build group) — semver minor. Changelog: no breaking changes, deprecations, or security fixes; additive only (Python 3.15 support, splash-screen options, unused hook updates). CI failing.

blocking

pyproject.toml:23uv.lock was not regenerated for this bump. The uv-lock prek hook fails in CI because the lockfile still pins pyinstaller==6.20.0 (and the transitive pyinstaller-hooks-contrib at 2026.5) while pyproject.toml now requires 6.21.0. Run uv lock and commit the resulting uv.lock diff (includes the pyinstaller-hooks-contrib 2026.5 → 2026.6 bump) before this can pass CI.

Prior-finding status

RESOLVED — pyproject.toml:44 — stale exclude-newer date blocked uv resolution of pyinstaller 6.21.0


@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a dependency-update review pipeline over the version bump:

  • Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
  • Extracted the changelog and release notes across the version range
  • Assessed compatibility with this project's usage and whether any code changes are required
  • Treated CI as the primary safety net
  • Scaled the review depth to the update's risk
  • Chose the verdict from semver risk, changelog findings, and CI status

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants