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
@changesets/cli (source) ^2.29.7 → ^3.0.0 age confidence
js-yaml 3.15.1 → 5.3.0 age confidence
pnpm (source) 10.34.5 → 11.22.0 age confidence
typescript (source) 5.9.3 → 7.0.2 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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.14.0

Compare Source

What's Changed

This is a performance release of protobuf-es. We've made substantial improvements to the runtime, while also reducing bundle size by 5%. Here are the results from our benchmarks (compared against v2.13.0):

fixture toBinary fromBinary toJson fromJson
general 4.66x 1.46x 2.29x 1.67x
scalar 2.91x 1.96x 1.74x 1.64x
repeated-scalar 4.37x 1.53x 3.06x 1.65x
map-scalar 4.43x 1.44x 2.42x 2.28x
repeated-message 5.27x 1.89x 1.71x 1.63x
map-message 5.21x 1.95x 1.81x 1.66x
user-tiny 1.44x 1.99x 1.49x 1.50x
user-normal 5.24x 1.99x 2.33x 2.03x

Individual changes are below:

New Contributors

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

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!

changesets/changesets (@​changesets/cli)

v3.0.0

Compare Source

Major Changes

  • #​2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #​2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #​1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #​1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #​1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #​2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #​2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #​2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #​1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #​1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #​1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #​2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #​1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #​1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #​1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #​2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #​1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

    This means the CLI flows will have minor changes, but they are largely the same.

    This change also fixes various issues related to enquirer like cancelling prompts crashing the CLI.

  • #​2090 3aae903 Thanks @​beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

    This means a peer dependency update is no longer assumed (forced) to be a breaking change.

    If the dependent package is not compatible with the peer's new release you should manually add a major changeset describing why and how to migrate.

Minor Changes

  • #​1121 ce2095d Thanks @​Sh031224! - Added new --major, --minor, --patch flags to the add command.

  • #​2135 fd7724a Thanks @​youdie006! - Allow comma-separated values in array-valued CLI flags: the --major, --minor, and --patch flags of the add command, and the --ignore flag of the version command. For example, --minor pkg-a,pkg-b is now equivalent to --minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.

  • #​2068 d03ffc1 Thanks @​bluwy! - Support {commit-short} placeholder for the snapshot.prereleaseTemplate config, which is a 7 character variant of {commit}

  • #​2061 c2db1dd Thanks @​Andarist! - Added a changeset publish-plan command to inspect which packages would be published or tagged, with optional JSON output.

  • #​2087 edc30c8 Thanks @​trueberryless! - Made the init command interactive. Running changeset init will now guide you through a set of intuitive prompts to configure your changelog generator, commit preferences, publish access, and base branch, rather than silently writing the default configuration file.

  • #​1969 2c7c043 Thanks @​marcalexiei! - Add a named export that mirrors the current default export

    The default export is slated for removal in the next major release, so this ensures a smoother transition path.

  • #​1879 c76b232 Thanks @​beeequeue! - Packages are now listed in alphabetical order when possible.

  • #​2129 369eb0b Thanks @​Andarist! - Commands supporting --output (such as status and publish-plan) can now be invoked with CHANGESETS_OUTPUT=path/to/file environment variable. This has the same effect as calling them with --output=path/to/file

  • #​2100 90b4ad0 Thanks @​Andarist! - Order releases into dependency-aware chunks so packages are grouped in publish order.

  • #​2136 2f9ca42 Thanks @​bluwy! - Remove confirmation prompt when adding a changeset. It will always add a changeset instead, and if the changeset is not desired, the user can edit or delete the file directly.

  • #​2155 5a8119b Thanks @​beeequeue! - Improved changeset publish failure handling. Errors are reported per package, successful publishes are still tagged when another package fails, and authentication retries avoid republishing completed packages.

  • #​2063 ed77176 Thanks @​Andarist! - Added changeset publish --from-pack-dir <dir> to publish packages from a previously created pack output directory.

  • #​2062 830443c Thanks @​Andarist! - Added a changeset pack command that requires --out-dir and writes publishable package tarballs plus an enriched publish-plan.json into that directory, either from the current workspace or from a saved publish plan via --from-plan.

  • #​1879 c76b232 Thanks @​beeequeue! - Choosing a change type now shows a preview of which part of the version it affects.

    Which packages should have a major (X.X.X) bump?

  • #​2129 369eb0b Thanks @​Andarist! - changeset publish and changeset tag can now be invoked with CHANGESETS_OUTPUT=path/to/file environment variable. They produce output in the NDJSON format.

  • #​2130 18bc470 Thanks @​beeequeue! - Allow unmatched glob patterns in the ignore config option.

  • #​2073 b9cbd80 Thanks @​bluwy! - Show if a package is private when selecting packages in changeset add

Patch Changes

  • #​1476 e0e1748 Thanks @​pralkarz! - Replace fs-extra usage with node:fs

  • #​2060 11bded4 Thanks @​Andarist! - Fixed changeset publish to respect ignored packages for both publishing and private package tagging.

  • #​2041 ce39c72 Thanks @​bluwy! - Enable guide line for add command and use box design for dependent patch bump note

  • #​2064 ffd65fc Thanks @​Andarist! - For pnpm projects, Changesets now match pnpm's native registry behavior more closely during unpublished package checks. Both scope-based publishConfig registry overrides and publishConfig.registry are now ignored.

  • #​2002 6db2c21 Thanks @​Andarist! - Lazy-load CLI commands so changeset only loads the code needed for the command being run.

  • #​2097 8c88f6a Thanks @​Andarist! - Route package manager calls through their respective CLIs during publish (npm, pnpm, yarn). Notably, Yarn Berry publishes now let Yarn update workspace protocol ranges as part of the publish process.

  • [

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on monday"
  • 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.

@changeset-bot

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

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ed92f7a

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 3 times, most recently from 1725a30 to 2e2c018 Compare August 23, 2026 17:36
@renovate
Update npm deps
ed92f7a 
Generated by renovateBot
@renovate
renovate Bot force-pushed the renovate/major-npm-deps branch from 2e2c018 to ed92f7a Compare August 31, 2026 01:15
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