chore(deps): update ⬆️ mise-packages - #1045
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
Renovate Release NotesGenerated from Renovate's update table by the Packages that cannot be summarized from GitHub releases are listed explicitly below. astral-sh/ruff (aqua:astral-sh/ruff)0.16.5: 0.16.5Release NotesReleased on 2026-08-27. Preview features
Bug fixes
Server
DocumentationContributorsInstall ruff 0.16.5Install prebuilt binaries via shell scriptcurl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.16.5/ruff-installer.sh | shInstall prebuilt binaries via powershell scriptpowershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/ruff/releases/download/0.16.5/ruff-installer.ps1 | iex"Download ruff 0.16.5Verifying GitHub Artifact AttestationsThe artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI: gh attestation verify <file-path of downloaded artifact> --repo astral-sh/ruffYou can also download the attestation from GitHub and verify against that directly: gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>astral-sh/uv (aqua:astral-sh/uv)0.12.7: 0.12.7Release NotesReleased on 2026-08-27. Python
Enhancements
Preview features
Bug fixes
Other changesInstall uv 0.12.7Install prebuilt binaries via shell scriptcurl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/uv/releases/download/0.12.7/uv-installer.sh | shInstall prebuilt binaries via powershell scriptpowershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/uv/releases/download/0.12.7/uv-installer.ps1 | iex"Download uv 0.12.7Verifying GitHub Artifact AttestationsThe artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI: gh attestation verify <file-path of downloaded artifact> --repo astral-sh/uvYou can also download the attestation from GitHub and verify against that directly: gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>crate-ci/typos (aqua:crate-ci/typos)v1.49.1: v1.49.1[1.49.1] - 2026-08-27Fixes
golangci/golangci-lint (aqua:golangci/golangci-lint)v2.13.2: v2.13.2
If you value it, consider supporting us, the maintainers and linter authors. We appreciate it! ❤️ For key updates, see the changelog. Changelog
sst/opencode (aqua:sst/opencode)v1.18.25: v1.18.25CoreBugfixes
v1.18.24: v1.18.24CoreBugfixes
Improvements
DesktopBugfixes
Thank you to 3 community contributors:
zellij-org/zellij (aqua:zellij-org/zellij)v0.45.1: Release v0.45.1This is a small patch release (mostly) set to address some issues discovered in the latest Notable changes
Full Changelog: zellij-org/zellij@v0.45.0...v0.45.1 Please Support the Zellij Developer ❤️Zellij is a labor of love and is provided free and open-source to anyone who wishes to use it. Zellij will never display ads or collect your data. To help sustain the project, please consider a recurring donation so that the developer can pay their bills: https://github.com/sponsors/imsnif anthropics/claude-code (github:anthropics/claude-code)v2.1.250: v2.1.250What's changed
v2.1.248: v2.1.248What's changed
backnotprop/plannotator (github:backnotprop/plannotator)v0.27.9: v0.27.9Follow @plannotator on X for updates Missed recent releases?
What's New in v0.27.9Eleven pull requests, one of them from @leoreisdias. Two threads run through the release. Browser-integrated agents can now read a plan or an annotate session and leave comments on it through WebMCP, instead of scraping the page. And the raw-HTML annotation surface gained a Refresh action along with a published set of seams so other applications can run that surface as Plannotator ships it. A Windows uninstall fix and a pre-release QA pass close it out. Browser agents can read your document and comment on itAn agent that runs inside the browser, such as Codex's browser or Claude Code's browser, has until now had to work out what is on the page by reading the DOM. Plan review and every annotate surface (markdown, raw HTML, live app, folder) now register a small tool catalog on The catalog is deliberately narrow. Three rules make this safe to ship without a consent dialog. Decisions stay with the human: no tool approves, denies, submits, closes, stages or marks anything viewed, and a test pins the catalog so none can be added quietly. An agent may edit or remove only the comments it created, which are stamped Without the API there is no footprint at all. Feature detection is one The nudges are what keep an agent in step with you. Every response carries codes computed from state the page already holds, so the agent learns on the call it was going to make anyway that you added a comment, that your composer is open, that the file changed on disk, or that the live app navigated to another page. A header indicator appears after the first tool call, and a Settings toggle turns the whole provider off and on. One product change comes with it. Code review is phase 2 and is not in this release.
Refresh rendered HTML from diskMarkdown annotate sessions pick up an agent's edits as soon as the file changes on disk. Rendered HTML sessions kept showing the snapshot they loaded at startup, so the review surface went stale the moment the agent rewrote the report you were reading. @leoreisdias added a Refresh action for local Review turned up a share-link race that predated the feature. The share request context included the identity of the resolver, and that identity changes as a side effect of its own success, so the first short link created on an HTML session discarded its own result. That is fixed with a regression test. A browser verification run found two more: the singular toast read "1 annotation no longer match the HTML", and a browser reload after a refresh reverted the page to the startup snapshot because The version diff that a refresh used to cost you is back as well, recomputed rather than dropped. That fix arrived with the QA pass below.
The HTML annotation surface, packaged for hostsApplications built on
Every seam is additive and defaults to today's behavior, and Plannotator's own app passes the same defaults. The one deliberate change you will see in Plannotator is that chip: annotations a Refresh could not re-anchor now carry it in the panel as well as in the toast, and it clears on the next refresh that re-anchors them. The rest was held to a real-browser A/B over an annotate session driven identically on both builds, with header, chrome and overlay-marker captures matching after normalizing minted ids and the port.
Renderers that load when they are neededMermaid, Graphviz, KaTeX and the identity dictionary used to ride every document read. They now load on demand, while Plannotator's own apps import eager entries as their first import and render exactly as before, typesetting math on the first commit with no frame of raw TeX. On the share portal the entry chunk drops from 1,831,133 to 1,211,620 gzip bytes, with the Graphviz engine and the Mermaid runtime becoming lazy chunks fetched only when a diagram is on the page. For a host that bundles by route, roughly a megabyte of renderer leaves the document-read closure. The raw-HTML viewer's 185 KB bridge script can also be served as a separately cached asset now. A host passes Two rounds of adoption feedback followed the first npm release. The default KaTeX loader moved into its own module so a host that registers its own loader can alias the package default out of its build entirely. Mermaid's own First edit in the atomic editor lands soonerThe Workspaces team measured the cost of clicking into the markdown editor and filed the numbers as #1401. Reproducing it in Plannotator showed that the part that grows with document size was not CodeMirror's layout measurement, as first suspected, but three editor extensions each forcing a synchronous parse of the whole document at mount. Windows uninstall no longer stalls on the PATH editCI caught this one. The uninstall lifecycle smoke test failed three times in a row on a single Windows run with "Could not remove ... from the Windows user PATH", while passing on every other run. The same run's cleanup killed several orphaned browser processes, which turned out to be the cause.
Both PowerShell scripts now write
Pre-release QAA review pass before tagging turned up six things worth fixing, all of them shipped here. An HTML root that became unreadable, replaced by a directory or stripped of read permission, used to throw: Pi left Reply threading became one shared rule.
Additional Changes
Install / UpdatemacOS / Linux: curl -fsSL https://plannotator.ai/install.sh | bashWindows: irm https://plannotator.ai/install.ps1 | iexClaude Code Plugin: Run Pi: Update OpenCode: Clear cache and restart: rm -rf ~/.bun/install/cache/@​plannotatorWhat's Changed
Community
Full Changelog: backnotprop/plannotator@v0.27.8...v0.27.9 PyCQA/isort (pipx:isort)9.0.1: 9.0.1🪲 Fixes
Other changes
Full Changelog: PyCQA/isort@9.0.0...9.0.1 Skipped PackagesGitHub Release Notes Unavailable
|
This PR contains the following updates:
0.16.4→0.16.50.12.6→0.12.70.12.81.49.0→1.49.11.50.02.13.1→2.13.21.18.23→1.18.250.45.0→0.45.10.206.0→0.208.10.209.0(+1)v2.1.247→v2.1.250v2.1.252(+1)v0.27.8→v0.27.9v0.27.10v0.18.3→v0.18.4v0.18.59.0.0→9.0.1Release notes are maintained in a PR comment by the
renovate-release-notes-commentworkflow.Configuration
📅 Schedule: (in timezone America/Los_Angeles)
* 3-5 * * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.