build(deps): update dependency sphinx-autobuild to v2025 (hotfix/5.11)
Metadata
Current evaluation
Closed unmerged after uv could not resolve sphinx-autobuild 2025.8.25 in uv.lock; Renovate stopped tracking future 2025.x updates for this branch.
Resolution: closed stale
Reason: Renovate reported a uv.lock resolution failure and warned not to merge the PR; it was then closed without merging, so Renovate ignored future 2025.x releases.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This PR contains the following updates:
| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [sphinx-autobuild](https://redirect.github.com/sphinx-doc/sphinx-autobuild#readme) ([changelog](https://redirect.github.com/sphinx-doc/sphinx-autobuild/blob/main/NEWS.rst)) | `==2024.10.3` → `==2025.8.25` |  |  |
---
### Release Notes
<details>
<summary>sphinx-doc/sphinx-autobuild (sphinx-autobuild)</summary>
### [`v2025.8.25`](https://redirect.github.com/sphinx-doc/sphinx-autobuild/compare/2024.10.03...2025.08.25)
[Compare Source](https://redirect.github.com/sphinx-doc/sphinx-autobuild/compare/2024.10.03...2025.08.25)
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "every weekend" in timezone Etc/UTC, Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/canonical/craft-application).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My40My4yIiwidXBkYXRlZEluVmVyIjoiNDMuNDMuMiIsInRhcmdldEJyYW5jaCI6ImhvdGZpeC81LjExIiwibGFiZWxzIjpbIlBSOiBEZXBlbmRlbmNpZXMiXX0=-->
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed unmerged after uv could not resolve sphinx-autobuild 2025.8.25 in uv.lock; Renovate stopped tracking future 2025.x updates for this branch. | |
| stealth/space-bunny-alpha | — | closed stale | Renovate’s sphinx-autobuild 2025.8.25 update in PR #1017 was closed unmerged after uv.lock dependency resolution failed; future 2025.x updates were ignored. | |
| stealth/space-bunny-alpha | — | closed stale | Renovate’s sphinx-autobuild 2025.8.25 update in #1017 was closed unmerged after uv.lock regeneration failed; Renovate then disabled future 2025.x updates. | |
| stealth/space-bunny-alpha | — | closed stale | Renovate's sphinx-autobuild 2025.8.25 update for hotfix/5.11 was closed unmerged after uv.lock generation failed to resolve Python 3.10 dependencies. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without merging due to a uv.lock dependency resolution failure. Renovate flagged an artifact update problem and will ignore future sphinx-autobuild v2025.x updates. The dependency bump was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging due to a uv.lock dependency resolution failure. Renovate will ignore future sphinx-autobuild 2025.x updates unless manually upgraded or the branch is renamed to trigger a replacement PR. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#1085
(confidence 70%)
Later build: update lockfile commit added sphinx-autobuild 2025.8.25.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2434 build(deps): update dependency sphinx-autobuild to v2025 (main) | charmcraft | closed | Renovate's sphinx-autobuild 2025.8 update in #2434 was closed unmerged after uv.lock regeneration failed; future 2025.x updates were ignored. | |
| #895 build(deps): update dependency sphinx-autobuild to v2025 (hotfix/5.9) | craft-application | closed | Closed unmerged after uv could not resolve sphinx-autobuild 2025.8.25 for Python 3.10; Renovate then ignored future 2025.x updates. | |
| #165 build(deps): update dependency sphinx-autobuild to v2025 | craft-platforms | closed | Closed unmerged after Renovate could not update uv.lock for sphinx-autobuild 2025.8.25 on Python 3.10; no fixing commit landed. | |
| #883 build(deps): update dependency sphinx-autobuild to v2025 (main) | craft-application | closed | Renovate PR #883 was closed unmerged after uv could not resolve sphinx-autobuild 2025.8.25 for Python 3.10; 2025.8.25 later entered uv.lock via #1085 (2a6a7320). | |
| #436 build(deps): update dependency sphinx-autobuild to v2025 | starbase | closed | Closed unmerged: sphinx-autobuild 2025.8.25 required Python >=3.11, so uv could not resolve the Python 3.10 lock split; Renovate ignored future 2025.x updates. | |
| #188 build(deps): update dependency sphinx-autobuild to v2025 (main) | craft-platforms | closed | Renovate's sphinx-autobuild 2025 update was closed unmerged after uv could not resolve uv.lock for Python 3.10; no update landed. | |
| #456 build(deps): update dependency sphinx-autobuild to v2025 (main) | starbase | closed | Closed unmerged after uv could not resolve sphinx-autobuild 2025.8.25 on supported Python 3.10; Renovate is now ignoring future 2025.x updates. | |
| #32 build(deps): update dependency sphinx-autobuild to v2025 | craft-artifacts | closed | Closed unmerged: sphinx-autobuild 2025.8.25 requires Python 3.11, so uv.lock could not resolve the Python 3.10 environment; the same update was later retried in #46. | |
| #938 build(deps): update dependency sphinx-autobuild to v2025 (hotfix/5.10) | craft-application | closed | PR #938 was closed unmerged after uv could not resolve sphinx-autobuild 2025.8.25 for Python 3.10/Questing; no 2025 update landed, and Renovate stopped proposing 2025.x updates. | |
| #1030 build(deps): update dependency sphinx-autobuild to v2025 (main) | craft-providers | closed | Dependency update to sphinx-autobuild v2025.8.25 closed due to Python 3.10 incompatibility. The new version requires Python >=3.11, causing uv.lock resolution to fail. |