chore(deps-dev): bump pyinstaller from 6.20.0 to 6.21.0#261
chore(deps-dev): bump pyinstaller from 6.20.0 to 6.21.0#261dependabot[bot] wants to merge 1 commit into
Conversation
rtibblesbot
left a comment
There was a problem hiding this comment.
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:46pinsexclude-newer = "2026-06-03T00:00:00Z", which predates pyinstaller 6.21.0's publish date (2026-06-13).uvtherefore 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 bumpexclude-newerpast 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
|
@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>
ea29620 to
82f51a5
Compare
rtibblesbot
left a comment
There was a problem hiding this comment.
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:23 — uv.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
Bumps pyinstaller from 6.20.0 to 6.21.0.
Release notes
Sourced from pyinstaller's releases.
Changelog
Sourced from pyinstaller's changelog.