Skip to content

Update npm deps (major) - #975

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-npm-deps
Open

Update npm deps (major)#975
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-npm-deps

Conversation

@renovate

@renovate renovate Bot commented Feb 10, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@babel/core (source) ^7.27.1 → ^8.0.0 age confidence
@bufbuild/protobuf (source) ^1.10.0 → ^2.0.0 age confidence
@bufbuild/protoc-gen-es (source) ^1.10.0 → ^2.0.0 age confidence
js-yaml 3.15.1 → 5.2.3 age confidence
pnpm (source) 10.34.5 → 11.20.0 age confidence
typescript (source) 5.9.3 → 7.0.2 age confidence

Release Notes

babel/babel (@​babel/core)

v8.0.1

Compare Source

💥 Breaking Change
  • babel-core, babel-plugin-transform-object-rest-spread, babel-plugin-transform-runtime, babel-preset-env, babel-standalone

v8.0.0

Compare Source

👓 Spec Compliance
💥 Breaking Change
  • babel-cli, babel-node, babel-plugin-proposal-decorators, babel-plugin-transform-classes, babel-plugin-transform-function-name, babel-plugin-transform-modules-commonjs, babel-plugin-transform-object-rest-spread, babel-plugin-transform-parameters, babel-plugin-transform-react-constant-elements, babel-plugin-transform-regenerator, babel-preset-env, babel-register
  • babel-plugin-transform-runtime, babel-runtime-corejs3, babel-runtime
  • babel-parser
🐛 Bug Fix
  • babel-generator
  • babel-plugin-transform-modules-systemjs
📝 Documentation
🏠 Internal
🏃‍♀️ Performance
bufbuild/protobuf-es (@​bufbuild/protobuf)

v2.13.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.12.1...v2.13.0

v2.12.1

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.12.0...v2.12.1

v2.12.0

Compare Source

What's Changed
New Contributors

Full Changelog: bufbuild/protobuf-es@v2.11.0...v2.12.0

v2.11.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.10.2...v2.11.0

v2.10.2

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.10.1...v2.10.2

v2.10.1

Compare Source

What's Changed
New Contributors

Full Changelog: bufbuild/protobuf-es@v2.10.0...v2.10.1

v2.10.0

Compare Source

What's Changed
New Contributors

Full Changelog: bufbuild/protobuf-es@v2.9.0...v2.10.0

v2.9.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.8.0...v2.9.0

v2.8.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.7.0...v2.8.0

v2.7.0

Compare Source

What's Changed

[!IMPORTANT]

TypeScript 5.9 includes breaking changes to lib.d.ts, forcing us to change return types for some functions from Uint8Array to Uint8Array<ArrayBuffer>. See #​1200 for details.

Full Changelog: bufbuild/protobuf-es@v2.6.3...v2.7.0

v2.6.3

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.6.2...v2.6.3

v2.6.2

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.6.1...v2.6.2

v2.6.1

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.6.0...v2.6.1

v2.6.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.5.2...v2.6.0

v2.5.2

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.5.1...v2.5.2

v2.5.1

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.5.0...v2.5.1

v2.5.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.4.0...v2.5.0

v2.4.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.3.0...v2.3.1

v2.3.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.2.5...v2.3.0

v2.2.5

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.2.4...v2.2.5

v2.2.4

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.2.3...v2.2.4

v2.2.3

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.2.2...v2.2.3

v2.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.2.1...v2.2.2

v2.2.1

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.2.0...v2.2.1

v2.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.1.0...v2.2.0

v2.1.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.0.0...v2.1.0

v2.0.0

Compare Source

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";

let user = create(UserSchema, {
  firstName: "Homer",
  lastName: "Simpson",
  active: true,
});

const bytes = toBinary(UserSchema, user);

If you use proto3, messages are now plain objects. Files with proto2 and editions use the prototype chain to track field presence.

This approach solves several outstanding issues, such as:

  • #​397 Provide custom options at runtime
  • #​551 Generated types allow assigning wrong message type if it is a superset of the target type
  • #​414 Improvements for proto2 required
  • #​738 type-save full enum value names
  • #​928 Better interop with 3rd party frameworks requiring plain objects
  • #​508 JSON types

[!TIP]

Take a look at the upgrade guide to learn more.

[!NOTE]

Connect-ES does not support version 2 yet. We will update it shortly.

Contributors

Thanks to @​srikrsna-buf for his contributions to v2!

nodeca/js-yaml (js-yaml)

v5.2.3

Compare Source

Fixed
  • Prevent prototype fallback when resolving tags and mapping entries, #​782.
  • Resolve !!timestamp years 0000-0099 correctly, #​775.
  • Preserve implicit null mapping values before document markers and reject
    unpaired mapping event streams, #​784.
  • Preserve folded scalar values with tab-indented lines when round-tripping a
    parsed AST through present(); dump() and loading are unaffected, #​780.

v5.2.2

Compare Source

Fixed
  • Quote flow scalars where a colon precedes a flow indicator, #​773.
Security
  • Avoid exponential parsing time for nested flow sequence pairs.

v5.2.1

Compare Source

Fixed
  • Add Map support to !!omap (should work when realMapTag used)
Security
  • Remove quadratic complexity from !!omap addItem. Regression from v5
    (usually not critical, because YAML11_SCHEMA is not default anymore).

v5.2.0

Compare Source

Added
  • Added maxTotalMergeKeys (10000) loader option to limit the total number of
    keys processed by YAML merge (<<) across one load() / loadAll() call.
  • Added maxAliases (-1) loader option to limit the number of YAML aliases per
    document.
Removed
  • maxMergeSeqLength replaced with maxTotalMergeKeys for limiting YAML merge
    processing.
Fixed
  • Round-trip of integers with exponential form (>= 1e21)

v5.1.0

Compare Source

Added
  • Collection tags can finalize an incrementally populated carrier into a
    different result value.
Changed
  • [breaking] quoteStyle now selects the preferred quote style; use the
    restored forceQuotes option to force quoting non-key strings.

v5.0.0

Compare Source

Added
  • Added named exports for schemas, tags, parser events and AST utilities.
  • Reworked JSON_SCHEMA and CORE_SCHEMA with spec-compliant scalar resolution
    rules, and added YAML11_SCHEMA.
  • Added realMapTag for lossless mappings with non-string and complex keys.
    Object-based mappings now reject complex keys instead of stringifying them.
  • Added dump() transform option for changing the generated AST before
    rendering.
  • Added dump() options seqInlineFirst, flowBracketPadding,
    flowSkipCommaSpace, flowSkipColonSpace, quoteFlowKeys, quoteStyle and
    tagBeforeAnchor.
  • Added formal data layers (events and AST) for modular data pipelines.
    • Added low-level parser (to events), presenter and visitor APIs.
  • Added the YAML Test Suite to the
    test set.
Changed
  • See the migration guide for upgrade notes.
  • Rewritten in TypeScript and reorganized the public API around flat named
    exports.
  • Reduced the set of exported schemas:
    • YAML 1.2 schemas: CORE_SCHEMA (loader default), JSON_SCHEMA,
      FAILSAFE_SCHEMA.
    • YAML11_SCHEMA, a combination of all YAML 1.1 tags (YAML 1.1 does not
      specify a schema, only "types").
  • load/dump default behaviour is now specified exactly via schemas:
    • load uses CORE_SCHEMA, without !!merge by default.
    • dump uses YAML11_SCHEMA + CORE_SCHEMA for the quoting check, to
      guarantee backward compatibility by default.
  • !!set is now loaded as a JavaScript Set.
  • Replaced the Type API with a tags API. Similar, but more precise and
    simpler. See examples for details. Tags can be defined via
    defineScalarTag(), defineSequenceTag() and defineMappingTag(), or as a
    spread + override of an existing tag.
  • Renamed Schema.extend() to Schema.withTags().
  • Expanded YAML 1.2 conformance and improved handling of directives, document
    markers, block keys, multiline scalars, tag syntax and other things.
  • load() now throws on empty input instead of returning undefined.
  • Moved browser builds to the js-yaml/browser export.
  • Deprecated the loadAll signature with an iterator (still works, but is a
    candidate for removal).
Removed
  • Removed deprecated safeLoad(), safeLoadAll() and safeDump() exports.
  • Removed DEFAULT_SCHEMA and the nested types export.
  • Removed loader options onWarning, legacy and listener.
  • Removed dumper options styles, replacer, noCompatMode, condenseFlow,
    quotingType and forceQuotes. Renamed noArrayIndent to seqNoIndent.
    Formatting and representation are now configured through presenter options,
    schemas and tag definitions. See migration guide on how to replace.
  • Removed support for importing internal files from lib/.

v4.3.1

Compare Source

v4.3.0

Compare Source

v4.2.0

Compare Source

Added
  • Added docs/safety.md with notes about processing untrusted YAML.
  • Added maxDepth (100) loader option. Not a problem, but gives a better
    exception instead of RangeError on stack overflow.
  • Added maxMergeSeqLength (20) loader option. Not a problem after merge fix,
    but an additional restriction for safety.
  • Added sourcemaps to dist/ builds.
Changed
  • Stop resolving numbers with underscores as numeric scalars, #​627.
  • Switched dev toolchains to Vite / neostandard.
  • Updated demo.
  • Reorganized tests.
  • dist/ files are no longer kept in the repository.
Fixed
  • Fix parsing of properties on the first implicit block mapping key, #​62.
  • Fix trailing whitespace handling when folding flow scalar lines, #​307.
  • Reject top-level block scalars without content indentation, #​280.
  • Ensure numbers survive round-trip, #​737.
  • Fix test coverage for issue #​221.
  • Fix flow scalar trailing whitespace folding, #​307.
  • Fix digits in YAML named tag handles.
Security
  • Fix potential DoS via quadratic complexity in merge - deduplicate repeated
    elements (makes sense for malformed files > 10K).

v4.1.1

Compare Source

Security
  • Fix prototype pollution issue in yaml merge (<<) operator.

v4.1.0

Compare Source

Added
  • Types are now exported as yaml.types.XXX.
  • Every type now has options property with original arguments kept as they were
    (see yaml.types.int.options as an example).
Changed
  • Schema.extend() now keeps old type order in case of conflicts
    (e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as abcd instead of cbad).

v4.0.0

Compare Source

Changed
  • Check migration guide in docs for details of all breaking changes.
  • Breaking: "unsafe" tags !!js/function, !!js/regexp, !!js/undefined are
    moved to js-yaml-js-types package.
  • Breaking: removed safe* functions. Use load, loadAll, dump
    instead which are all now safe by default.
  • yaml.DEFAULT_SAFE_SCHEMA and yaml.DEFAULT_FULL_SCHEMA are removed, use
    yaml.DEFAULT_SCHEMA instead.
  • yaml.Schema.create(schema, tags) is removed, use schema.extend(tags) instead.
  • !!binary now always mapped to Uint8Array on load.
  • Reduced nesting of /lib folder.
  • Parse numbers according to YAML 1.2 instead of YAML 1.1 (01234 is now decimal,
    0o1234 is octal, 1:23 is parsed as string instead of base60).
  • dump() no longer quotes :, [, ], (, ) except when necessary, #​470, #​557.
  • Line and column in exceptions are now formatted as (X:Y) instead of
    at line X, column Y (also present in compact format), #​332.
  • Code snippet created in exceptions now contains multiple lines with line numbers.
  • dump() now serializes undefined as null in collections and removes keys with
    undefined in mappings, #​571.
  • dump() with skipInvalid=true now serializes invalid items in collections as null.
  • Custom tags starting with ! are now dumped as !tag instead of !<!tag>, #​576.
  • Custom tags starting with tag:yaml.org,2002: are now shorthanded using !!, #​258.
Added
  • Added .mjs (es modules) support.
  • Added quotingType and forceQuotes options for dumper to configure
    string literal style, #​290, #​529.
  • Added styles: { '!!null': 'empty' } option for dumper
    (serializes { foo: null } as "foo: "), #​570.
  • Added replacer option (similar to option in JSON.stringify), #​339.
  • Custom Tag can now handle all tags or multiple tags with the same prefix, #​385.
Fixed
  • Astral characters are no longer encoded by dump(), #​587.
  • "duplicate mapping key" exception now points at the correct column, #​452.
  • Extra commas in flow collections (e.g. [foo,,bar]) now throw an exception
    instead of producing null, #​321.
  • __proto__ key no longer overrides object prototype, #​164.
  • Removed bower.json.
  • Tags are now url-decoded in load() and url-encoded in dump()
    (previously usage of custom non-ascii tags may have led to invalid YAML that can't be parsed).
  • Anchors now work correctly with empty nodes, #​301.
  • Fix incorrect parsing of invalid block mapping syntax, #​418.
  • Throw an error if block sequence/mapping indent contains a tab, #​80.
pnpm/pnpm (pnpm)

v11.20.0: pnpm 11.20

Compare Source

Minor Changes

  • Security fix. Affects projects using namedRegistries on pnpm 11.1.0–11.19.x. It is semi-breaking for those projects — see "If you use named registries" below.

    The lockfile recorded no marker for which registry a package came from. Packages were keyed by name@version alone, and entry lookup went through refToRelative(ref, name), so a dependency you declared against one registry could be satisfied by an entry that was actually resolved from another. When two registries served the same name and version, both collapsed onto a single packages: entry and whichever resolved first decided the tarball every consumer got.

    That is a package-substitution risk: a package you expect from your private registry could be installed from a different registry that publishes the same name and version, and the lockfile recorded nothing that would let you tell.

    Packages resolved from a named registry are now recorded under registry-qualified keys (<name>@<registryName>:<version>, e.g. foo@work:1.0.0), so each registry gets its own entry and the lockfile pins which one a dependency came from.

    The lockfile format version is unchanged. Registry-qualified keys appear only for packages resolved from a named registry, so a project that does not use namedRegistries sees no difference, and older pnpm versions keep reading the file.

If you use named registries

Your next non-frozen install re-keys those entries, which shows up as a lockfile diff. Commit it — that diff is the fix being applied. Review it: an entry that moves to a registry you did not expect is worth investigating.

Everyone working on the project should be on this version or newer before you do. An older pnpm reads the re-keyed lockfile fine — frozen installs are unaffected — but it does not produce registry-qualified keys itself, so any install that updates the lockfile writes those entries back to the old shape, and the next install on a current pnpm re-qualifies them. The result is a lockfile that flips back and forth, and while it is in the old shape the project is exposed again. Because the lockfile format version is deliberately unchanged, pnpm cannot detect this and warn you about it.

There is no setting to keep the old behavior: the old shape is the vulnerability.

Tarball URLs that follow the standard registry layout are no longer written to the lockfile for named-registry packages; they are recomputed from the namedRegistries setting on demand.

To use named registries, map your aliases in pnpm-workspace.yaml:

namedRegistries:
  work: https://npm.enterprise.example.com/
New built-in npmjs: alias

npmjs: now resolves to https://registry.npmjs.org/ with no configuration, alongside the existing gh: alias for GitHub Packages. It pins a dependency to the public registry even when registry points elsewhere, such as an internal proxy:

{ "dependencies": { "left-pad": "npmjs:^1.3.0" } }

npm: cannot do this — it is the alias protocol (npm:<name>@<range>) and resolves through whatever registry points at.

If you mirror or proxy npmjs, point the alias at your mirror:

namedRegistries:
  npmjs: https://npm.internal.example.com/

Built-in registry URLs are also the prefixes a lockfile's recorded tarball URL is matched against when pnpm verifies a package. Without the override, an entry whose tarball URL is on registry.npmjs.org is verified against the public registry rather than your mirror. This only affects lockfiles that record such URLs — a canonical URL for your configured registry is omitted from the lockfile and unaffected — and only when a tarball-URL, minimumReleaseAge, or trustPolicy check runs. Overriding the alias is the same escape hatch GHES users already have for gh.

Every alias the lockfile references must stay in namedRegistries: reading an entry whose alias is gone fails with ERR_PNPM_MISSING_NAMED_REGISTRY rather than silently falling back to the default registry, since that would fetch a different package. Renaming an alias re-resolves the packages that used it.

Named registry aliases that shadow a reserved dependency specifier prefix (file, link, workspace, runtime, npm, jsr, ...) are now rejected with ERR_PNPM_RESERVED_NAMED_REGISTRY_NAME instead of being silently shadowed by the corresponding resolver.

pnpm licenses and pnpm sbom now keep the two artifacts apart as well: license records carry the registry alias, and SBOM components carry the purl repository_url qualifier.

Patch Changes

  • An empty http-proxy, https-proxy, proxy, or no-proxy value — from the .npmrc, pnpm-workspace.yaml, the CLI, or the HTTP_PROXY / HTTPS_PROXY / PROXY / NO_PROXY environment variables — no longer fails the install with ERR_PNPM_INVALID_PROXY. Empty settings read as unset, so a shell exporting HTTP_PROXY= disables the proxy, and an empty proxy= in the .npmrc no longer suppresses HTTPS_PROXY #​13533.

    proxy=false in the .npmrc or proxy: false in pnpm-workspace.yaml now turns proxying off instead of being read as a proxy host named false. false and null on https-proxy / http-proxy / no-proxy read as unset, and on the command line they are ordinary host names, since a flag carries its value verbatim.

  • The env lockfile no longer pins @pnpm/exe alongside pnpm when the wanted pnpm version is 12 or newer. From v12 the unscoped pnpm package is itself the native executable, so @pnpm/exe is not published for it and resolving it would fail. The engine identity check now verifies the native binary through whichever package ships it.

  • lexCompare and nerfDart are now published as @pnpm/text.ordinal-comparator and @pnpm/config.registry-auth-key. Use these instead of @pnpm/util.lex-comparator and @pnpm/config.nerf-dart.

  • Fixed the order in which pnpm matches a lockfile's recorded tarball URL against known registry URLs. Two registry URLs of equal length were previously ordered arbitrarily, so which one a tarball URL matched could differ between runs.

  • Dependency resolution is faster: package metadata is now filtered once per packument instead of once per dependency edge when minimumReleaseAge is active, and parsed semver versions and ranges are reused instead of re-parsed on every comparison.

  • Security: pnpm rebuild now refuses a lockfile whose packages key carries a path traversal in the package name (e.g. ../../../escaped@1.0.0), instead of running that package's lifecycle scripts and linking its bins in a directory outside the virtual store. Such a name is rejected with ERR_PNPM_INVALID_DEPENDENCY_NAME.

Platinum Sponsors

Bit
OpenAI

Gold Sponsors

Sanity Discord Vite
SerpApi 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.

@changeset-bot

changeset-bot Bot commented Feb 10, 2025 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 1725a30

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from ec20fba to 5984392 Compare February 23, 2025 07:17
@renovate renovate Bot changed the title Update npm deps (major) fix(deps): update npm deps (major) Mar 24, 2025
@renovate renovate Bot changed the title fix(deps): update npm deps (major) Update npm deps (major) Apr 8, 2025
@renovate renovate Bot changed the title Update npm deps (major) fix(deps): update npm deps (major) May 7, 2025
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 3 times, most recently from 7b9a50a to 55c3842 Compare May 19, 2025 18:38
@renovate renovate Bot changed the title fix(deps): update npm deps (major) Update npm deps (major) Jun 11, 2025
@renovate renovate Bot changed the title Update npm deps (major) fix(deps): update npm deps (major) Jun 16, 2025
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 4 times, most recently from 9044dc8 to 960beec Compare June 26, 2025 21:51
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from 960beec to fdf43be Compare July 9, 2025 13:48
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 2 times, most recently from 7c4eb9d to dd539cf Compare July 23, 2025 18:14
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from dd539cf to 461c094 Compare July 31, 2025 18:05
@renovate renovate Bot changed the title fix(deps): update npm deps (major) Update npm deps (major) Aug 2, 2025
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 2 times, most recently from c930a95 to e5cfad8 Compare August 10, 2025 13:21
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 6 times, most recently from 609c1c4 to ba36706 Compare August 19, 2025 22:00
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 2 times, most recently from ee8c002 to 1d306d0 Compare September 2, 2025 15:56
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from 1d306d0 to 534afe9 Compare September 8, 2025 00:52
@renovate renovate Bot changed the title Update npm deps (major) fix(deps): update npm deps (major) Sep 11, 2025
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 5 times, most recently from 583aa24 to d656845 Compare September 18, 2025 19:52
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 4 times, most recently from 9937424 to 672d652 Compare September 29, 2025 12:33
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch 6 times, most recently from 09d3612 to 436a405 Compare October 2, 2025 17:33
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from 8b59252 to ef810f6 Compare August 17, 2026 19:12
@renovate renovate Bot changed the title fix(deps): update npm deps (major) Update npm deps (major) Aug 17, 2026
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from ef810f6 to c2e9427 Compare August 17, 2026 19:13
@renovate
Update npm deps
1725a30 
Generated by renovateBot
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from c2e9427 to 1725a30 Compare August 17, 2026 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants