chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #61 · comarkdown/vscode-comark

renovate · 2025-09-08T17:13:20Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@types/node (source)	`^25.9.3` → `^25.9.4`	devDependencies	patch
pnpm (source)	`11.7.0` → `11.8.0`	packageManager	minor
vscode	`^1.75.0` → `^1.125.0`	engines	minor

Release Notes

pnpm/pnpm (pnpm)

`v11.8.0`

Compare Source

Minor Changes

c112b61: Added a --dry-run option to pnpm install. It runs a full dependency resolution and reports what an install would change, but writes nothing to disk (no lockfile, no node_modules) and always exits with code 0. This mirrors the preview semantics of npm install --dry-run #7340.
179ebc4: pnpm run --no-bail now exits with a non-zero exit code when any of the executed scripts fail, while still running every matched script to completion. This makes the exit-code behavior of --no-bail consistent between recursive and non-recursive runs (recursive runs already failed at the end). Previously, a non-recursive pnpm run --no-bail always exited with code 0, even when a script failed #8013.
0474a9c: Added support for generating Node.js package maps at node_modules/.package-map.json during isolated and hoisted installs. Added the node-experimental-package-map setting to inject the generated map into pnpm-managed Node.js script environments, and the node-package-map-type setting to choose between standard and loose package maps.
dcededc: pnpm sbom now marks components reachable only through devDependencies with CycloneDX scope: "excluded" and the cdx:npm:package:development property. The excluded scope documents "component usage for test and other non-runtime purposes", which matches the semantics of a devDependency; the property is the CycloneDX npm-taxonomy marker emitted by @cyclonedx/cyclonedx-npm, so both modern (scope) and existing (property) consumers are covered. Components reachable at runtime (including installed optionalDependencies) omit scope and default to required.
1495cb0: Added per-package SBOM generation with --out and --split flags. Use --out out/%s.cdx.json to write one SBOM per workspace package to individual files, or --split for NDJSON output to stdout. When --filter selects a single package, the SBOM root component now uses that package's metadata. Workspace inter-dependencies (workspace: protocol) and their transitive dependencies are included. Author, repository, and license fall back to the root manifest when the package doesn't define them.
293921a: feat(view): support searching project manifest upward when package name is omitted

When running pnpm view without a package name, the command now searches
upward for the nearest project manifest (package.json, package.yaml, or package.json5) and uses its name field.
If the manifest exists but lacks a name field, an error is thrown.

This change also replaces the find-up dependency with empathic for
improved performance and consistency across workspace tools.

Patch Changes

29ab905: Fixed pnpm update overriding the version range policy of a named catalog whose name parses as a version (e.g. catalog:express4-21). The catalog: reference carries no pinning of its own, so the prefix from the catalog entry (such as ~) is now preserved instead of being widened to ^ #10321.
bee4bf4: Security: validate config dependency names and versions from the env lockfile (pnpm-lock.yaml) before using them to build filesystem paths. A committed lockfile with a traversal-shaped configDependencies name (such as ../../PWNED) or version (such as ../../../PWNED) could previously cause pnpm install to create symlinks or write package files outside node_modules/.pnpm-config and the store. Names must now be valid npm package names and versions must be exact semver versions; the same validation is applied to optional subdependencies of config dependencies, and to the legacy workspace-manifest format before any lockfile is written. See GHSA-qrv3-253h-g69c.
96bdd57: Fix link: workspace protocol switching to file: after pnpm rm is run from inside a workspace package whose target workspace dependency has its own dependencies, when injectWorkspacePackages: true is set. Follow-up to #10575, which fixed the same symptom for workspace packages without dependencies.
302a2f7: No longer warn about using both packageManager and devEngines.packageManager when the two fields pin the same package manager at the same version with the same integrity hash (e.g. both pnpm@11.5.1+sha512.…). Previously the hash was stripped from the legacy packageManager field but not from devEngines.packageManager, so even identical specifications looked like a mismatch #12028.

The warning still fires on any genuine divergence, and several cases now state the specific reason instead of a single generic message: a different package manager, a different version, or contradictory integrity hashes for the same version.
3f0fb21: Fixed the progress line showing leftover characters from external processes that write to the terminal between progress updates (e.g. an SSH passphrase prompt would leave a fragment like added 0sa':). The interactive reporter now redraws each frame in place, erasing to the end of the display before reprinting, so any such remnants are cleared #12350.
564619f: Fixed pnpm approve-builds reporting "no packages awaiting approval" when a build-script dependency whose approval was revoked (e.g. after git stash drops the allowBuilds from pnpm-workspace.yaml) is re-added. The revoked packages are now correctly recorded in .modules.yaml so approve-builds can find them. #12221
3d1fd20: Skip the redundant "target bin directory already contains an exe called node" warning on Windows when the existing node.exe already matches the target (same hard link or identical content) pnpm/pnpm#12203.
1b02b47: Fix macOS Gatekeeper blocking native binaries (.node, .dylib, .so) by removing the com.apple.quarantine extended attribute after importing them from the store.

When pnpm imports files from its content-addressable store into node_modules, macOS preserves extended attributes, including com.apple.quarantine. If this xattr is present on a store blob (e.g. it was first written under a Gatekeeper-enabled app such as a Git client), it propagates to node_modules, and Gatekeeper blocks the native binary from loading even though pnpm already verified the file's integrity against the lockfile.

After importing a package, pnpm now strips com.apple.quarantine from its native binaries, matching Homebrew's behaviour of dropping quarantine from verified downloads. The cleanup is macOS-only, runs in a single batched xattr call per package, is restricted to native binaries (other files are untouched), and is non-fatal (it logs a warning on unexpected errors).

Fixes #11056
61969fb: Fix pnpm install with optimisticRepeatInstall incorrectly reporting Already up to date when pnpm-lock.yaml changed but project manifests did not. This affected workflows such as checking out or restoring only the lockfile #12100.

Also fixes checkDepsStatus to use the correct lockfile path when useGitBranchLockfile is enabled, so the optimistic fast-path and lockfile modification detection work with pnpm-lock.<branch>.yaml files instead of always stat'ing pnpm-lock.yaml. Merge-conflict detection now reads the resolved lockfile name as well, and with mergeGitBranchLockfiles enabled every pnpm-lock.*.yaml is scanned for modifications and conflicts. The git branch is now resolved by reading .git/HEAD directly (no process spawn) and uses the workspace directory rather than process.cwd().
5c12968: Fix recursive updates of transitive dependencies when the update command mixes transitive dependency patterns with direct dependency selectors. For example, pnpm up -r "@babel/core" uuid now updates matching transitive @babel/core dependencies even when uuid is a direct dependency selector #12103.
9d79ba1: Register the pnpm update --no-save flag in the CLI help and option parser.
0474a9c: Fixed pnpm import for Yarn v2 lockfiles when js-yaml v4 is installed.
9e0c375: Fixed pnpm install repeatedly prompting to remove and reinstall node_modules in a workspace package when enableGlobalVirtualStore is enabled. The post-install build step recorded a per-project node_modules/.pnpm virtual store directory in node_modules/.modules.yaml, overwriting the global <storeDir>/links value the install step had written. The next install then detected a virtual-store mismatch (ERR_PNPM_UNEXPECTED_VIRTUAL_STORE). The build step now derives the same global virtual store directory as the install step #12307.
223d060: Document the --cpu, --os and --libc flags in the output of pnpm install --help. These flags were already supported but were only documented on the website #12359.
e85aea2: Avoid reading README.md from disk when publishing if the publish manifest already provides a readme field. The README is now only read lazily, inside createExportableManifest, when it is actually needed.
3188ae7: Fixed pnpm peers check to accept loose peer dependency ranges such as >=3.16.0 || >=4.0.0- when the installed peer version satisfies the range #12149.
531f2a3: Fixed pnpm update rewriting a workspace: dependency that points at a local path (e.g. workspace:../packages/foo/dist) into a normalized link: or version-range specifier. Such specifiers are now preserved verbatim when the workspace protocol is preserved #3902.
fe66535: Fixed a lockfile non-convergence bug where an incremental install kept a duplicate transitive dependency that a fresh install would not produce. When a package is reused from the lockfile, its child edges are taken verbatim and bypass the preferred-versions walk, so a transitive dependency could stay pinned to an older version even after a direct dependency resolved to a higher version that satisfies the same range. The resolver now refreshes such a stale pin to the higher direct-dependency version during resolution — so the older version is never resolved or fetched, and the incremental result converges to the fresh one.
6d35338: pnpm install detects changes inside local file dependencies again. The optimistic repeat-install fast path only tracks manifest and lockfile modification times, so edits inside a local dependency's directory (or a repacked local tarball) were reported as "Already up to date". Projects with local file dependencies (file: and bare local path or tarball specifiers, declared directly or through pnpm.overrides) now always run a full install, which refetches those dependencies, matching pnpm v10 behavior #11795.
4ca9247: Preserve the existing Node.js runtime version prefix when resolving node@runtime:<range> to a concrete version.
30c7590: Create shorter CAFS temporary package directories to leave room for lifecycle scripts that create IPC socket paths under TMPDIR.
13815ad: Reporter output (warnings, progress) for pnpm store and pnpm config subcommands now goes to stderr instead of stdout. This fixes scripts that capture their stdout (e.g. PNPM_STORE=$(pnpm store path), pnpm config list --json | jq) from getting warnings mixed into the result.
1c05876: Avoid relinking unchanged child dependencies and remove stale child links during warm installs.
817f99d: Fixed lockfile churn where a package's transitivePeerDependencies could be dropped (and shift between packages) when the package participates in a dependency cycle. A cycle re-entry resolves against truncated children, so it must not be cached as "pure"; otherwise sibling occurrences of the same package short-circuit and lose transitive peers depending on traversal order #5108.
eba03e0: Fix pnpm install reporting "Already up to date" after a catalog entry in pnpm-workspace.yaml was reverted to a previous version. After an update modified a catalog, the workspace state cache stored the pre-update catalog versions, so reverting the entry back to its original version was not detected as an outdated state #12418.
3b54d79: pnpm update now keeps lockfile overrides that resolve through a catalog in sync with the catalog. Previously, when an override referenced a catalog (e.g. overrides: { foo: 'catalog:' }) and pnpm update bumped that catalog entry, the lockfile's catalogs advanced while the resolved overrides kept the old version. The resulting lockfile was internally inconsistent, so a later pnpm install --frozen-lockfile failed with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH.
9d0a300: Fixed pnpm version --recursive so it honors the workspace selection. In recursive mode the version bump now applies to the packages resolved from the workspace filter (selectedProjectsGraph), matching the behavior of pnpm publish --recursive, instead of always bumping every workspace package #11348.

microsoft/vscode (vscode)

The update addresses these issues

https://code.visualstudio.com/updates/v1_122

`v1.122.0`

Compare Source

https://code.visualstudio.com/updates/v1_122

`v1.121.0`

Compare Source

https://code.visualstudio.com/updates/v1_121

`v1.120.0`

Compare Source

https://code.visualstudio.com/updates/v1_120

`v1.119.1`

Compare Source

The update addresses these issues

https://code.visualstudio.com/updates/v1_119

`v1.119.0`

Compare Source

https://code.visualstudio.com/updates/v1_119

`v1.118.1`

Compare Source

Fixed GitHub Copilot CLI not working from VS Code.

https://code.visualstudio.com/updates/v1_118

`v1.118.0`

Compare Source

https://code.visualstudio.com/updates/v1_118

`v1.117.0`

Compare Source

https://code.visualstudio.com/updates/v1_117

`v1.116.0`

Compare Source

https://code.visualstudio.com/updates/v1_116

`v1.115.0`

Compare Source

https://code.visualstudio.com/updates/v1_115

`v1.114.0`

Compare Source

https://code.visualstudio.com/updates/v1_114

`v1.113.0`

Compare Source

https://code.visualstudio.com/updates/v1_113

`v1.112.0`

Compare Source

https://code.visualstudio.com/updates/v1_112

`v1.111.0`: March 2026 (version 1.111)

Compare Source

Welcome to the 1.111 release of Visual Studio Code, the first of our weekly Stable releases! This release further enhances the agent experience with agent permissions, agent-scoped hooks, easier agent debugging and troubleshooting, and more.

Happy Coding!

`v1.110.1`: February 2026 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.109.5`: January 2026 Recovery 5

Compare Source

The update addresses these issues
.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.109.4`

Compare Source

`v1.109.2`: January 2026 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.109.1`: January 2026 Recovery 1

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.109.0`: January 2026

Compare Source

Welcome to the January 2026 release of Visual Studio Code. In this release, we are further evolving VS Code to make it the home for multi-agent development.

Chat UX: chat just feels better and snappier with faster streaming, improved reasoning results, and a revamped editor inline chat
Agent Session Management: it's now easier to delegate tasks to agents across local, background, and cloud and jump in when needed
Agent Customization: build your own workflows using agent orchestrations, and have consistent results with Agent Skills and organization-wide customizations
Agent Extensibility: reuse your knowledge with Claude agent support and new Anthropic model capabilities, and enjoy rich chat interactions with MCP Apps
Agent Optimizations: agents work smarter with Copilot Memory and experience faster code search with external indexing
Agent Security & Trust: feel confident running terminal commands with sandboxing and effective auto-approval rules
Workbench & productivity: test your apps without leaving the editor with the new integrated browser

`v1.108.2`: December 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.108.1`: December 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.108.0`: December 2025

Compare Source

Welcome to the December 2025 release of Visual Studio Code.

Traditionally, the month of December is a time where our team focuses on cleaning up GitHub issues and pull requests across our repositories. This year, we managed to reduce our open issues by nearly 6,000 and triaged over a thousand more.

In addition to our housekeeping efforts, we have also made several improvements and feature updates across various areas of VS Code.

Happy Coding!

`v1.107.1`: November 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.107.0`: November 2025

Compare Source

Welcome to the November 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

VS Code now includes Agent HQ, background agents and custom agents for your org.

Agent HQ: You can use GitHub Copilot alongside your other coding agents to complete multiple tasks. Leverage background, cloud, or local agents and their relative strengths for the right job, all at the same time.
Background agents work in their own isolated workspaces, managed for you by VS Code.
Custom agents for organizations: Your team can now share custom agents at the org level.

`v1.106.3`: October 2025 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.106.2`: October 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.106.1`: October 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.106.0`: October 2025

Compare Source

Welcome to the October 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

AI	Productivity and UX	Enterprise
Plan complex coding tasks with the plan agent and monitor agent sessions across background agents Show more	Select text from deleted code in the diff editor Show more	Manage MCP server access with custom MCP registry Show more
Inline suggestions are now open source Show more	Experience the more modern, refreshed product icons Show more	Manage Linux devices with JSON policies Show more

`v1.105.1`: September 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.105.0`: September 2025

Compare Source

Welcome to the September 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

OS integration	Developer productivity	Agent tools
Get notified about task completion and chat responses Show more	Resolve merge conflicts with AI assistance Show more	Install MCP servers from the MCP marketplace Show more
Native authentication experience on macOS Show more	Pick up where you left off with the recent chats Show more	Use fully-qualified tool names to avoid conflicts Show more

`v1.104.3`: August 2025 Recovery 3

Compare Source

The update addresses these issues.

`v1.104.2`: August 2025 Recovery 2

Compare Source

The update addresses these issues.

`v1.104.1`: August 2025 Recovery 1

Compare Source

The update addresses these issues.

`v1.104.0`: August 2025

Compare Source

Welcome to the August 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Model flexibility	Security	Productivity
Let VS Code select the best model Show more	Confirm edits for sensitive files Show more	Remove distractions from chat file edits Show more
Contribute models through VS Code extensions Show more	Let agents run terminal commands safely Show more	Use AGENTS.md to add chat context Show more

`v1.103.2`: July 2025 Recovery 2

Compare Source

The update addresses these issues.

`v1.103.1`: July 2025 Recovery 1

Compare Source

The update adds GPT-5 prompt improvements, support for GPT-5 mini, and addresses these issues.

`v1.103.0`: July 2025

Compare Source

Welcome to the July 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

MCP	Chat	Productivity
Revamped tool picker experience Show more	Use GPT-5 in VS Code Show more	Check out multiple branches simultaneously with Git worktrees Show more
Enable more than 128 tools per agent request Show more	Restore to a previous good state with chat checkpoints Show more	Manage coding agent sessions in a dedicated view Show more

`v1.102.3`: June 2025 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.102.2`: June 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.102.1`: June 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.102.0`: June 2025

Compare Source

Welcome to the June 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Chat

Explore and contribute to the open sourced GitHub Copilot Chat extension (Read our blog post).
Generate custom instructions that reflect your project's conventions (Show more).
Use custom modes to tailor chat for tasks like planning or research (Show more).
Automatically approve selected terminal commands (Show more).
Edit and resubmit previous chat requests (Show more).

MCP

MCP support is now generally available in VS Code (Show more).
Easily install and manage MCP servers with the MCP view and gallery (Show more).
MCP servers as first-class resources in profiles and Settings Sync (Show more).

Editor experience

Delegate tasks to Copilot coding agent and let it handle them in the background (Show more).
Scroll the editor on middle click (Show more).
If you'd like to read these release notes online, go to Updates on code.visualstudio.com. Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

`v1.101.2`: May 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.101.1`: May 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.101.0`: May 2025

Compare Source

Welcome to the May 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

MCP

Expand your agent coding flow with support for prompts, resources, and sampling (Show more).
Access MCP servers that require authentication (Show more).
Debug MCP servers with development mode (Show more).
Publish MCP servers from an extension (Show more).

Chat

Group and manage related tools by combining them in a tool set (Show more).

Source Control

View files in Source Control Graph view (Show more).
Assign and track work for GitHub Copilot Coding Agent from within VS Code (Show more).

If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

`v1.100.3`: April 2025 Recovery 3

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.100.2`: April 2025 Recovery 2

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.100.1`: April 2025 Recovery 1

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.100.0`: April 2025

Compare Source

Welcome to the April 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Chat
- Custom instructions and reusable prompts (more...).
- Smarter results with tools for GitHub, extensions, and notebooks (more...).
- Image and Streamable HTTP support for MCP (more...).
Chat performance
- Faster responses on repeat chat requests (more...).
- Faster edits in agent mode (more...).
Editor experience
- Improved multi-window support for chat and editors (more...).
- Staged changes now easier to identify (more...).

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

`v1.99.3`: March 2025 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.99.2`: March 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.99.1`: March 2025 Recovery 1

Compare Source

The update has a fix for the security vulnerability in this issue.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.99.0`: March 2025

Compare Source

Welcome to the March 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Agent mode
- Agent mode is available in VS Code Stable. Enable it by setting chat.agent.enabled:true (more...).
- Extend agent mode with Model Context Protocol (MCP) server tools (more...).
- Try the new built-in tools in agent mode for fetching web content, finding symbol references, and deep thinking (more...).
Code editing
- Next Edit Suggestions is now generally available (more...).
- Benefit from fewer distractions such as diagnostics events while AI edits are applied in the editor (more...).
Chat
- Use your own API keys to access more language models in chat (preview) (more...).
- Easily switch between ask, edit, and agent mode from the unified chat experience (more...).
- Experience improved workspace search speed and accuracy with instant remote workspace indexing (more...).
Notebook editing
- Create and edit notebooks as easily as code files with support for edit and agent mode (more...).

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

`v1.98.2`: February 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.98.1`: February 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

`v1.98.0`: February 2025

Compare Source

Welcome to the February 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Next Edit Suggestions (preview) - Copilot predicts the next edit you are likely to make.
Agent mode (preview) - Copilot autonomously completes tasks.
Copilot Edits for notebooks - Iterate quickly on edits for your notebooks.
Code search - Let Copilot find relevant files for your chat prompt.
Terminal IntelliSense (preview) - Rich completion support for your terminal.
Drag & drop references - Quickly open peek references in a new editor.
Linux custom title bar - Custom title bar support for Linux enabled by default.
Unresolved diagnostics (preview) - Prompt when committing with unresolved diagnostics.
Soft-delete in source control - Move untracked files to trash instead of deleting them.
Custom instructions GA - Use custom instructions to tailor Copilot to your needs.

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to see new features as soon as possible? You can download the nightly [Insiders](https://code.visualstudio.com/ins

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2026-06-19T12:04:45Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (572 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
[WARN] deprecated @types/glob@9.0.0: This is a stub types definition. glob provides its own type definitions, so you do not need this installed.
Progress: resolved 12, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 0, added 0
Progress: resolved 16, reused 0, downloaded 0, added 0
Progress: resolved 17, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (572 entries in 5.8s)
Progress: resolved 138, reused 0, downloaded 0, added 0
Progress: resolved 440, reused 0, downloaded 0, added 0
Progress: resolved 569, reused 0, downloaded 0, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 1 version does not meet the minimumReleaseAge constraint:
  @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-17T12:04:27.874Z)

renovate Bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 0ce961c to 647e301 Compare September 18, 2025 05:34

renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 31afad9 to e82d82a Compare October 2, 2025 01:49

renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 95a8582 to edefacb Compare October 9, 2025 19:07

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from eae88ff to 633af8d Compare October 20, 2025 09:43

renovate Bot force-pushed the renovate/all-minor-patch branch from 633af8d to 45ce248 Compare October 28, 2025 12:02

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b178e20 to b9b1480 Compare November 10, 2025 17:12

renovate Bot force-pushed the renovate/all-minor-patch branch from b9b1480 to 42cf0fc Compare November 17, 2025 23:15

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 3bd18a5 to 57cb6a0 Compare December 9, 2025 18:11

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ad77787 to 005b857 Compare January 6, 2026 12:56

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 537b10d to 746620e Compare January 23, 2026 00:44

renovate Bot force-pushed the renovate/all-minor-patch branch from 746620e to f3e58a6 Compare February 4, 2026 10:57

renovate Bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 7fd9f31 to 015a901 Compare February 26, 2026 22:08

renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 4803dfe to 69827b9 Compare March 7, 2026 01:37

renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 2dd39e6 to 472abdf Compare March 12, 2026 18:47

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 73cbf08 to 52746fd Compare March 18, 2026 17:36

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 64b33d4 to 0654f25 Compare March 25, 2026 13:56

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b4f4303 to de1328b Compare April 3, 2026 13:23

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 25c12e3 to 33e2160 Compare April 10, 2026 05:52

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4ac7bf8 to 50df7f1 Compare May 21, 2026 15:11

chore(deps): update all non-major dependencies

5ee6ab5

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all non-major dependencies#61

chore(deps): update all non-major dependencies#61
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

renovate Bot commented Sep 8, 2025 •

edited

Loading

Uh oh!

renovate Bot commented Jun 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Sep 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

v1.111.0: March 2026 (version 1.111)

v1.110.1: February 2026 Recovery 1

v1.109.5: January 2026 Recovery 5

v1.109.2: January 2026 Recovery 2

v1.109.1: January 2026 Recovery 1

v1.109.0: January 2026

v1.108.2: December 2025 Recovery 2

v1.108.1: December 2025 Recovery 1

v1.108.0: December 2025

v1.107.1: November 2025 Recovery 1

v1.107.0: November 2025

v1.106.3: October 2025 Recovery 3

v1.106.2: October 2025 Recovery 2

v1.106.1: October 2025 Recovery 1

v1.106.0: October 2025

v1.105.1: September 2025 Recovery 1

v1.105.0: September 2025

v1.104.3: August 2025 Recovery 3

v1.104.2: August 2025 Recovery 2

v1.104.1: August 2025 Recovery 1

v1.104.0: August 2025

v1.103.2: July 2025 Recovery 2

v1.103.1: July 2025 Recovery 1

v1.103.0: July 2025

v1.102.3: June 2025 Recovery 3

v1.102.2: June 2025 Recovery 2

v1.102.1: June 2025 Recovery 1

v1.102.0: June 2025

Chat

MCP

Editor experience

v1.101.2: May 2025 Recovery 2

v1.101.1: May 2025 Recovery 1

v1.101.0: May 2025

MCP

Chat

Source Control

v1.100.3: April 2025 Recovery 3

v1.100.2: April 2025 Recovery 2

v1.100.1: April 2025 Recovery 1

v1.100.0: April 2025

v1.99.3: March 2025 Recovery 3

v1.99.2: March 2025 Recovery 2

v1.99.1: March 2025 Recovery 1

v1.99.0: March 2025

v1.98.2: February 2025 Recovery 2

v1.98.1: February 2025 Recovery 1

v1.98.0: February 2025

Configuration

Uh oh!

renovate Bot commented Jun 19, 2026

⚠️ Artifact update problem

File name: pnpm-lock.yaml

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Sep 8, 2025 •

edited

Loading

`v1.111.0`: March 2026 (version 1.111)

`v1.110.1`: February 2026 Recovery 1

`v1.109.5`: January 2026 Recovery 5

`v1.109.2`: January 2026 Recovery 2

`v1.109.1`: January 2026 Recovery 1

`v1.109.0`: January 2026

`v1.108.2`: December 2025 Recovery 2

`v1.108.1`: December 2025 Recovery 1

`v1.108.0`: December 2025

`v1.107.1`: November 2025 Recovery 1

`v1.107.0`: November 2025

`v1.106.3`: October 2025 Recovery 3

`v1.106.2`: October 2025 Recovery 2

`v1.106.1`: October 2025 Recovery 1

`v1.106.0`: October 2025

`v1.105.1`: September 2025 Recovery 1

`v1.105.0`: September 2025

`v1.104.3`: August 2025 Recovery 3

`v1.104.2`: August 2025 Recovery 2

`v1.104.1`: August 2025 Recovery 1

`v1.104.0`: August 2025

`v1.103.2`: July 2025 Recovery 2

`v1.103.1`: July 2025 Recovery 1

`v1.103.0`: July 2025

`v1.102.3`: June 2025 Recovery 3

`v1.102.2`: June 2025 Recovery 2

`v1.102.1`: June 2025 Recovery 1

`v1.102.0`: June 2025

`v1.101.2`: May 2025 Recovery 2

`v1.101.1`: May 2025 Recovery 1

`v1.101.0`: May 2025

`v1.100.3`: April 2025 Recovery 3

`v1.100.2`: April 2025 Recovery 2

`v1.100.1`: April 2025 Recovery 1

`v1.100.0`: April 2025

`v1.99.3`: March 2025 Recovery 3

`v1.99.2`: March 2025 Recovery 2

`v1.99.1`: March 2025 Recovery 1

`v1.99.0`: March 2025

`v1.98.2`: February 2025 Recovery 2

`v1.98.1`: February 2025 Recovery 1

`v1.98.0`: February 2025