chore: bump up all dependencies - #2459
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@milkdown/components
@milkdown/core
@milkdown/crepe
@milkdown/ctx
@milkdown/exception
@milkdown/kit
@milkdown/prose
@milkdown/transformer
@milkdown/utils
@milkdown/react
@milkdown/vue
@milkdown/plugin-automd
@milkdown/plugin-block
@milkdown/plugin-clipboard
@milkdown/plugin-collab
@milkdown/plugin-cursor
@milkdown/plugin-diff
@milkdown/plugin-emoji
@milkdown/plugin-highlight
@milkdown/plugin-history
@milkdown/plugin-indent
@milkdown/plugin-listener
@milkdown/plugin-prism
@milkdown/plugin-slash
@milkdown/plugin-streaming
@milkdown/plugin-tooltip
@milkdown/plugin-trailing
@milkdown/plugin-upload
@milkdown/preset-commonmark
@milkdown/preset-gfm
@milkdown/theme-nord
commit: |
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 14, 2026 18:44
13b7412 to
e5dc001
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 16, 2026 13:36
e5dc001 to
e243918
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 22, 2026 08:56
e243918 to
d722c84
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 25, 2026 04:48
d722c84 to
cb46a6a
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 30, 2026 07:37
cb46a6a to
83b3fd3
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 30, 2026 12:55
83b3fd3 to
4256b78
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 2, 2026 20:02
4256b78 to
32d89bd
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 4, 2026 00:50
32d89bd to
e82ac50
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 4, 2026 17:10
e82ac50 to
cbd507b
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 5, 2026 20:53
cbd507b to
6af2b63
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 6, 2026 00:54
6af2b63 to
5b1224e
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 6, 2026 12:34
5b1224e to
5ed4a58
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 7, 2026 01:36
5ed4a58 to
832556f
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 7, 2026 11:40
832556f to
e240dd5
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 7, 2026 18:42
e240dd5 to
f16925f
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
September 8, 2026 01:08
f16925f to
98c6c43
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.22.0→^3.0.0v1.9.0→v2.1.1v2.1.211.24.0→12.3.4^11.0.0→^12.0.0^1.0.0→^2.0.02.3.1^4.0.0→^5.0.0Release Notes
changesets/changesets (@changesets/cli)
v3.0.2Compare Source
Patch Changes
a0a4dc6Thanks @bluwy! - Add review message on pre exit1f4eb61,059f70a]:v3.0.1Compare Source
Patch Changes
fdfdc93Thanks @bluwy! - Update links in default generated.changeset/README.mdfiled0386b6]:v3.0.0Compare Source
Major Changes
#2128
7113c01Thanks @Andarist! - Renamed thechangeset tagcommand tochangeset git-tag.#2074
3599e47Thanks @bluwy! - Set supported package manager versions in"engines"field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.#1860
92b1c1bThanks @mixelburg! -changeset versionnow 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
--snapshotmode.#1482
df424a4Thanks @Andarist! - Bumped supported Node versions to^22.11 || ^24 || >=26#1994
062530bThanks @bluwy! - Theprettieroption in.changeset/config.jsonhas been removed in favor offormat.formatsupports"auto","prettier","oxfmt","deno", and"dprint", andfalsedisables formatting. If you previously usedprettier: false, migrate toformat: falseor remove the option to use automatic formatter detection.#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.#2145
f5887ffThanks @Andarist! - Removed Yarn Classic support#2097
8c88f6aThanks @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-assignlatesttag. npm registry itself does that and such packages will continue to be released withlatesttag (and not with the configured prerelease tag).#1879
c76b232Thanks @beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.#1655
db46911Thanks @bluwy! - Update@manypkg/get-packageswhich drops support for detecting packages in Bolt monorepos and adds support for npm monorepos#1651
e1df862Thanks @bluwy! - Remove support for the--sinceMasterflag forchangeset status. Use--since=masteror--since=maininstead.#2117
813bbf3Thanks @bluwy! - Remove thepre.jsoninitialVersionsproperty and handling as it's unused internally#1961
07278a7Thanks @beeequeue! -CommitFunctionscan now be both sync and async, and thedefaultCommitFunctionsare now sync.#1482
df424a4Thanks @Andarist! - From now on this package is going to be published as ES module.#1652
a0b5326Thanks @bluwy! - Remove support for the deprecated___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshotsconfig. Thesnapshot.useCalculatedVersionconfig should be used instead.#2186
3910adfThanks @Andarist! - Private packages are no longer versioned by default. SetprivatePackagestotrueto opt into versioning and tagging them, or setprivatePackages.versiontotrueto version them without tagging.#1879
c76b232Thanks @beeequeue! - Migrated fromenquirer+@inquirer/launch-editorto@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
enquirerlike cancelling prompts crashing the CLI.#2090
3aae903Thanks @beeequeue! - Peer dependencies now bump packages that depend on them bypatchinstead ofmajor.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
majorchangeset describing why and how to migrate.Minor Changes
#1121
ce2095dThanks @Sh031224! - Added new--major,--minor,--patchflags to theaddcommand.#2135
fd7724aThanks @youdie006! - Allow comma-separated values in array-valued CLI flags: the--major,--minor, and--patchflags of theaddcommand, and the--ignoreflag of theversioncommand. For example,--minor pkg-a,pkg-bis now equivalent to--minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.#2068
d03ffc1Thanks @bluwy! - Support{commit-short}placeholder for thesnapshot.prereleaseTemplateconfig, which is a 7 character variant of{commit}#2061
c2db1ddThanks @Andarist! - Added achangeset publish-plancommand to inspect which packages would be published or tagged, with optional JSON output.#2087
edc30c8Thanks @trueberryless! - Made theinitcommand interactive. Runningchangeset initwill 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
2c7c043Thanks @marcalexiei! - Add a named export that mirrors the currentdefaultexportThe
defaultexport is slated for removal in the next major release, so this ensures a smoother transition path.#1879
c76b232Thanks @beeequeue! - Packages are now listed in alphabetical order when possible.#2129
369eb0bThanks @Andarist! - Commands supporting--output(such asstatusandpublish-plan) can now be invoked withCHANGESETS_OUTPUT=path/to/fileenvironment variable. This has the same effect as calling them with--output=path/to/file#2100
90b4ad0Thanks @Andarist! - Order releases into dependency-aware chunks so packages are grouped in publish order.#2136
2f9ca42Thanks @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
5a8119bThanks @beeequeue! - Improvedchangeset publishfailure handling. Errors are reported per package, successful publishes are still tagged when another package fails, and authentication retries avoid republishing completed packages.#2063
ed77176Thanks @Andarist! - Addedchangeset publish --from-pack-dir <dir>to publish packages from a previously created pack output directory.#2062
830443cThanks @Andarist! - Added achangeset packcommand that requires--out-dirand writes publishable package tarballs plus an enrichedpublish-plan.jsoninto that directory, either from the current workspace or from a saved publish plan via--from-plan.#1879
c76b232Thanks @beeequeue! - Choosing a change type now shows a preview of which part of the version it affects.#2129
369eb0bThanks @Andarist! -changeset publishandchangeset tagcan now be invoked withCHANGESETS_OUTPUT=path/to/fileenvironment variable. They produce output in the NDJSON format.#2130
18bc470Thanks @beeequeue! - Allow unmatched glob patterns in theignoreconfig option.#2073
b9cbd80Thanks @bluwy! - Show if a package is private when selecting packages inchangeset addPatch Changes
#1476
e0e1748Thanks @pralkarz! - Replacefs-extrausage withnode:fs#2060
11bded4Thanks @Andarist! - Fixedchangeset publishto respect ignored packages for both publishing and private package tagging.#2041
ce39c72Thanks @bluwy! - Enable guide line foraddcommand and use box design for dependent patch bump note#2064
ffd65fcThanks @Andarist! - For pnpm projects, Changesets now match pnpm's native registry behavior more closely during unpublished package checks. Both scope-basedpublishConfigregistry overrides andpublishConfig.registryare now ignored.#2002
6db2c21Thanks @Andarist! - Lazy-load CLI commands sochangesetonly loads the code needed for the command being run.#2097
8c88f6aThanks @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.#2132
d35bb77Thanks @cyphercodes! - Improve publish error handling for npm and pnpm JSON errors. Changesets now skips npm 11 already-published errors that omitcode, correctly skips pnpm 11 already-published errors, and retries pnpm 11ERR_PNPM_OTP_NON_INTERACTIVEpublish failures in delegated interactive mode.#2160
162419dThanks @beeequeue! - Added or modified thefilesproperty in the manifest. This should not change any behavior.#2009
44df27dThanks @bluwy! - Usecacfor CLI arg parsing and handling#2113
b8222e6Thanks @Andarist! - Fixed publish error printing for pnpm 11.#2065
0598e83Thanks @Andarist! - Improvedchangeset publishauth handling by removing the preflight OTP requirement check and falling back to interactive auth when the package manager reports that authentication is required.#2065
0598e83Thanks @Andarist! -changeset publishnow reads initial OTP values from npm and pnpm environment variables.#2171
3257f57Thanks @beeequeue! - Enabled Node's Compile Cache to improve CLI startup speed.#1570
d099e43Thanks @pralkarz! - Removed extra leftover code related to Changesets v1#2113
b8222e6Thanks @Andarist! - Fixed accidental success logs on failed npm publishes#1616
609046cThanks @bluwy! - Removeterm-sizedependency#1476
e0e1748Thanks @pralkarz! - Replacedspawndamnitwithtinyexec#584
6c79210Thanks @Andarist! - Avoid an infinite loop when git commands fail to execute when Changesets try to retrieve commits that added files.#2177
b5e1762Thanks @Andarist! - Avoid writing anundefinedversion when updating dependencies in unversioned private packages.#2163
5f8d925Thanks @Andarist! - Update dependency ranges in the workspace rootpackage.json.#2004
169b128Thanks @ghostdevv! - Replacepicocolorswithnode:util'sstyleText#1640
2ad65e0Thanks @bluwy! - Remove deprecated flag warnings, including--updateChangelog,--isPublic,--skipCI, and--commitUpdated dependencies [
e0e1748,6d1f384,a736a20,062530b,6a05002,ee10723,88f2abb,c76b232,6a05002,694396c,d03ffc1,df424a4,b5e1762,c19b112,03d4479,162419d,b9407b3,4c26f2f,96b65ee,3628cab,8f7b607,db46911,b83787f,2c7c043,01f4da4,813bbf3,6a05002,c2348fc,fc42514,062530b,07278a7,c98af4c,df424a4,a0b5326,e0e1748,6c79210,b5e1762,3910adf,5f8d925,169b128,18bc470,6a05002,3aae903,062530b,96b65ee]:changesets/action (changesets/action)
v2.1.1Compare Source
Patch Changes
da1ea29Thanks @KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v2v2.1.0Compare Source
Minor Changes
3b7c71cThanks @bluwy! - Add acwdinput to the root action,/select-mode,/version,/pack, and/publishsub-actions to set the current working directory to execute Changesets in. This input existed in v1 but was incorrectly removed.Patch Changes
6f58ba3Thanks @bluwy! - Updatepr-statusmessage to link to the new faq pagev2.0.0Compare Source
Major Changes
#692
cb3f011Thanks @Andarist! - Release commits and tags are now pushed using the GitHub API by default.Replace the
commit-modeinput with the booleanpush-with-git-cliinput. Setpush-with-git-cli: trueto continue using the Git CLI.Regardless of the push mode, custom GitHub tokens must be passed explicitly through the
github-tokeninput. TheGITHUB_TOKENenvironment variable and credentials configured byactions/checkoutor embedded in remote URLs are not substitutes for this input. When the Git CLI is enabled,github-tokentakes precedence over those repository credentials.#680
ca57073Thanks @bluwy! - Add a newpush-git-tagsoption that complementscreate-github-releasesto control specifically if git tags should be created but not GitHub releases.If
create-github-releaseswas previously set tofalse, which also indirectly disabled git tag creation, git tags will now be created instead by default. If this is not desired, setpush-git-tagstofalseexplicitly.#657
4f718b5Thanks @Andarist! - Removed compatibility support for old Changesets v1.#681
7359107Thanks @bluwy! - Rename the root action inputs and outputs to better match the sub-actions' conventions.Inputs:
version->version-scriptpublish->publish-scriptcommit->commit-messagetitle->pr-titlebranch->pr-base-branchOutputs:
pull-request-number->pr-number#674
164652bThanks @bluwy! - Remove support for passing custom GitHub token through the GITHUB_TOKEN environment variable. It should be passed to thegithub-tokeninput instead.#659
5649ff4Thanks @bluwy! - Removecwdoption forchangesets/action. Use the stepworking-directoryoption instead to change the directory.#673
823cf74Thanks @bluwy! - Update to Changesets v3 packages#695
469993cThanks @bluwy! - Removed.npmrchandling when theNPM_TOKENenvironment variable is set.Authentication should be handled via Trusted Publishing instead. If a token is still needed, use
actions/setup-nodeto set it up instead via theregistry-urloption. Check out the updated action README for more information of setting up npm authentication in GitHub Actions.#668
0eae789Thanks @bluwy! - Rename the input and output names to kebab-case instead of camelCase to match the official GitHub actions patternMinor Changes
#656
a12d90dThanks @bluwy! - Add new/select-mode,/version, and/publishsub-actions to better control version and publish steps#678
f71ae04Thanks @Andarist! - Published packages detection done through stdout parsing was replaced with one based on the shared output file usingCHANGESETS_OUTPUTenvironment variable. When using custom scripts this environment variable should always be passed down to the Changesets CLI invocations.Patch Changes
#699
5b307d3Thanks @Andarist! - Validate that projects use Changesets CLI v3 and direct Changesets CLI v2 users tochangesets/action@v1.#697
84d78c6Thanks @Andarist! - Allow custom publish scripts to complete without a Changesets output file, warning that GitHub releases and git tags cannot be created when that file is missing.#670
5a8b9b7Thanks @Andarist! - Authenticate git CLI pushes with the configured GitHub token using Git extra headers instead of writing to a global.netrcfile.#670
5a8b9b7Thanks @Andarist! - Derive the Git server URL from the GitHub Actions context when configuring git CLI authentication to support GitHub Enterprise Server setups.#688
219ea82Thanks @Andarist! - Remove thesetup-git-userinput. Complete custom Git identities are now preserved automatically, whilegithub-actions[bot]is configured as a fallback before creating local release commits or tags.pnpm/pnpm (pnpm)
v12.3.4: pnpm 12.3.4Compare Source
Patch Changes
Sped up dependency resolution in large workspaces #14352.
pnpm 12 now accepts the boolean settings as command-line flags on every command that takes them in pnpm 11, for example
pnpm install --unsafe-perm,pnpm add foo --offline, andpnpm install --dangerously-allow-all-builds. pnpm 12 rejected them withunexpected argument, which failed every install on Vercel, whose build runspnpm install --unsafe-perm#14346.pnpm removenow accepts--unsafe-perm, the same flagpnpm install,pnpm add, andpnpm updatetake.Platinum Sponsors
Gold Sponsors
v12.3.3: pnpm 12.3.3Compare Source
Patch Changes
Fixed concurrent installs sharing a store occasionally failing with an ENOENT error while importing a package file #14353.
Sped up writing the lockfile in large workspaces #14352.
Sped up dependency resolution in large workspaces #14352.
pnpm now runs through Node.js when it was installed by a tool that skips build scripts, such as Vercel's
packageManagerprovisioning, Bun, Deno, ornpm install --ignore-scripts. Those installs previously failed withsyntax error near unexpected token ')'. They still cannot run pnpm on Windows. On macOS only a shell can start it #14346.Platinum Sponsors
Gold Sponsors
v12.3.2: pnpm 12.3.2Compare Source
Patch Changes
pnpm audit --fix updateno longer aborts when a vulnerable package has no safe version inside its declared range [#1450Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.