Skip to content

chore(deps): update all dependencies - #114

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all
Open

chore(deps): update all dependencies#114
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Feb 1, 2026 •
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 Adoption Passing Confidence Type Update
@changesets/changelog-github (source) 0.5.1 → 1.0.0 age adoption passing confidence devDependencies major
@changesets/cli (source) 2.29.7 → 3.0.1 age adoption passing confidence devDependencies major
@types/node (source) ^24 → ^26.0.0 age adoption passing confidence devDependencies major
actions/checkout v5 → v7 age adoption passing confidence action major
actions/setup-node v5 → v7 age adoption passing confidence action major
changesets/action v1 → v2.1.1 age adoption passing confidence action major
codecov/codecov-action v5 → v7 age adoption passing confidence action major
jest (source) 30.2.0 → 30.4.2 age adoption passing confidence devDependencies minor
lerna (source) 9.0.0 → 10.0.1 age adoption passing confidence devDependencies major
node (source) 24.13 → 24.19 age adoption passing confidence minor
node 22 → 24 age adoption passing confidence uses-with major
prettier (source) 3.6.2 → 3.9.6 age adoption passing confidence devDependencies minor
rimraf 6.0.1 → 6.1.3 age adoption passing confidence devDependencies minor
ts-jest (source) 29.4.4 → 29.4.12 age adoption passing confidence devDependencies patch
typescript (source) 5.9.3 → 7.0.2 age adoption passing confidence devDependencies major

Release Notes

changesets/changesets (@​changesets/changelog-github)

v1.0.0

Compare Source

Major Changes
Minor Changes

  • #​2059 070f531 Thanks @​jycouet! - Add an opt-in, experimental template option to render changelog lines from tokens ({summary}, {ref}, {pull}, {commit}, {authors}). Default output is unchanged. The token syntax may change in a patch release; pin the version if you rely on it.

  • #​1871 dfefc4e Thanks @​mihkeleidast! - Use GITHUB_REPOSITORY as the default repo when no repo option is configured

  • #​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.

Patch Changes

v0.7.0

Compare Source

Minor Changes

v0.6.0

Compare Source

Minor Changes
Patch Changes

v0.5.2

Compare Source

Patch Changes
changesets/changesets (@​changesets/cli)

v3.0.1

Compare Source

Patch Changes

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

v2.31.1

Compare Source

Patch Changes
  • #​2159 15cf592 Thanks @​ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successful npm info --json output in an array. The unwrapped output made changeset publish treat every package as unpublished and fail attempting to republish existing versions.

v2.31.0

Compare Source

Minor Changes

  • #​1889 96ca062 Thanks @​mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.

  • #​1873 42943b7 Thanks @​mixelburg! - Respond to --help on all subcommands. Previously, --help was only handled when it was the sole argument; passing it alongside a subcommand (e.g. changeset version --help) would silently execute the command instead. Now --help always exits early and prints per-command usage when a known subcommand is provided, or the general help text otherwise.

Patch Changes

v2.30.0

Compare Source

Minor Changes

  • #​1840 057cca2 Thanks @​wotan-allfather! - Add --since flag to add command

    The add command now supports a --since flag that allows you to specify which branch, tag, or git ref to use when detecting changed packages. This is useful for gitflow workflows where you have multiple target branches and the baseBranch config option doesn't cover all use cases.

    Example: changeset add --since=develop

    If not provided, the command falls back to the baseBranch value in your .changeset/config.json.

  • #​1845 2b4a66a Thanks @​Andarist! - Delegate OTP prompting to the package manager instead of handling it in-process. This allows Changesets to use the package manager's native web auth support.

  • #​1774 667fe5a Thanks @​bluwy! - Support importing custom commit option ES module. Previously, it used require() which only worked for CJS modules, however now it uses import() which supports both CJS and ES modules.

  • #​1839 73b1809 Thanks @​leochiu-a! - Add a --message (-m) flag to changeset add (and default changeset) so the changeset summary can be provided from the command line. When --message is present, the summary prompt is skipped while the final confirmation step is kept.

  • #​1806 0e8e01e Thanks @​luisadame! - Changeset CLI can now be run from the nested directories in the project, where the .changeset directory has to be found in one of the parent directories

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • 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 1, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7cf425c

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

@codecov

codecov Bot commented Feb 1, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.92%. Comparing base (477925e) to head (8881f36).
⚠️ Report is 15 commits behind head on main.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #114   +/-   ##
=======================================
  Coverage   77.92%   77.92%           
=======================================
  Files           6        6           
  Lines         154      154           
  Branches       44       52    +8     
=======================================
  Hits          120      120           
- Misses         33       34    +1     
+ Partials        1        0    -1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 352b726 to cbf6bf5 Compare February 8, 2026 01:51
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from d56f3eb to 24ec97b Compare February 16, 2026 02:10
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 2313497 to 46ee23f Compare February 24, 2026 16:58
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from ed9eb96 to 8b49057 Compare March 3, 2026 10:14
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from 029d529 to dd4e95b Compare March 11, 2026 13:07
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 1b76071 to 8881f36 Compare March 13, 2026 22:45
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from b7495d6 to 73e58d9 Compare March 26, 2026 17:38
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from c5e00f5 to 8711e53 Compare April 3, 2026 13:21
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from db223a9 to a05d7c9 Compare April 15, 2026 04:57
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 2ce1831 to 7ee7d1f Compare May 21, 2026 18:37
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from c28da50 to 18187b7 Compare June 2, 2026 16:11
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from da88bd5 to ecc2d22 Compare June 11, 2026 02:12
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from 76f8f99 to 54166c7 Compare June 25, 2026 02:36
@renovate
renovate Bot force-pushed the renovate/all branch 6 times, most recently from dbe1a9f to 5db1d1e Compare July 1, 2026 22:04
@renovate
renovate Bot force-pushed the renovate/all branch 6 times, most recently from c12f800 to 1adbdce Compare July 14, 2026 06:07
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 7db4055 to 5556c79 Compare July 21, 2026 06:52
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