You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#21287113c01 Thanks @Andarist! - Renamed the changeset tag command to changeset git-tag.
#20743599e47 Thanks @bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.
#186092b1c1b 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.
#1994062530b 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.
#219096b65ee 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.
#20978c88f6a 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).
#1879c76b232 Thanks @beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.
#1655db46911 Thanks @bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos
#1651e1df862 Thanks @bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.
#2117813bbf3 Thanks @bluwy! - Remove the pre.jsoninitialVersions property and handling as it's unused internally
#196107278a7 Thanks @beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.
#1482df424a4 Thanks @Andarist! - From now on this package is going to be published as ES module.
#1652a0b5326 Thanks @bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.
#21863910adf 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.
#1879c76b232 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.
#20903aae903 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.
#21287113c01 Thanks @Andarist! - Renamed the changeset tag command to changeset git-tag.
#20743599e47 Thanks @bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.
#186092b1c1b 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.
#1994062530b 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.
#219096b65ee 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.
#20978c88f6a 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).
#1879c76b232 Thanks @beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.
#1655db46911 Thanks @bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos
#1651e1df862 Thanks @bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.
#2117813bbf3 Thanks @bluwy! - Remove the pre.jsoninitialVersions property and handling as it's unused internally
#196107278a7 Thanks @beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.
#1482df424a4 Thanks @Andarist! - From now on this package is going to be published as ES module.
#1652a0b5326 Thanks @bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.
#21863910adf 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.
#1879c76b232 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.
#20903aae903 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.
This version was pushed to npm by GitHub Actions, a new releaser for @changesets/cli since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
PR-Codex overview
This PR updates various package versions in package.json and pnpm-lock.yaml, mainly focusing on upgrading @changesets/cli from 2.29.5 to 3.0.0 and adjusting dependencies and their versions across multiple packages.
Detailed summary
Upgraded @changesets/cli from 2.29.5 to 3.0.0.
Updated next dependencies to use @babel/core@7.29.7 instead of @babel/core@7.28.4.
Modified utf-8-validate versions from 6.0.5 to 6.0.6 in multiple packages.
Updated storybook and related packages to use utf-8-validate@6.0.6.
Adjusted tailwindcss and vite dependencies to point to yaml@2.9.0.
Various other minor version updates across multiple packages.
The following files were skipped due to too many changes: pnpm-lock.yaml
✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}
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
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@walletconnect/sign-client@2.23.7. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm yargs is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/yargs@17.7.3. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
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
DependenciesPull requests that update a dependency filejavascriptPull requests that update Javascript code
0 participants
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.
dependabot
Bot
added
Dependencies
Bumps @changesets/cli from 2.29.5 to 3.0.0.
Release notes
Sourced from @changesets/cli's releases.
... (truncated)
Changelog
Sourced from @changesets/cli's changelog.
... (truncated)
Commits
f442221Version Packages (#2235)e3facadVersion Packages (next) (#2228)c98af4cDo not bump ignored independent packages when exiting pre mode (#2092)496ca21Build(deps-dev): Bump the development-dependencies group with 6 updates (#2225)d1053acBuild(deps): Bump the production-dependencies group across 1 directory with 2...68ea6ecFix linked and fixed glob patterns expansion (#2222)c1b6f8cfix missing coloring of name (#2218)a53d1f8Remove old atlaskit changelogs (#2217)7bcb2d2Build(deps-dev): Bump the development-dependencies group across 1 directory w...baa658dVersion Packages (next) (#2192)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@changesets/clisince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)PR-Codex overview
This PR updates various package versions in
package.jsonandpnpm-lock.yaml, mainly focusing on upgrading@changesets/clifrom2.29.5to3.0.0and adjusting dependencies and their versions across multiple packages.Detailed summary
@changesets/clifrom2.29.5to3.0.0.nextdependencies to use@babel/core@7.29.7instead of@babel/core@7.28.4.utf-8-validateversions from6.0.5to6.0.6in multiple packages.storybookand related packages to useutf-8-validate@6.0.6.tailwindcssandvitedependencies to point toyaml@2.9.0.