Skip to content

chore(deps): update changesets monorepo - #78

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/changesets-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/changesets-monorepo

Conversation

@renovate

@renovate renovate Bot commented Feb 20, 2026 •

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
@changesets/changelog-github (source) 0.3.0 → 0.7.0 age confidence
@changesets/cli (source) 2.14.1 → 2.31.1 age confidence

Release Notes

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

v0.7.0

Compare Source

Minor Changes

v0.6.0

Compare Source

Minor Changes
Patch Changes

v0.5.2

Compare Source

Patch Changes

v0.5.1

Compare Source

Patch Changes

v0.5.0

Compare Source

Minor Changes
  • #​1185 a971652 Thanks @​Andarist! - package.json#exports have been added to limit what (and how) code might be imported from the package.
Patch Changes

v0.4.8

Compare Source

Patch Changes

v0.4.7

Compare Source

Patch Changes

v0.4.6

Compare Source

Patch Changes

v0.4.5

Compare Source

Patch Changes

v0.4.4

Compare Source

Patch Changes

v0.4.3

Compare Source

Patch Changes

v0.4.2

Compare Source

Patch Changes

v0.4.1

Compare Source

Patch Changes

v0.4.0

Compare Source

Minor Changes
  • #​564 707002d Thanks @​Andarist! - It's now possible to specify multiple authors of a change by using multiple author: @someuser lines.
Patch Changes
changesets/changesets (@​changesets/cli)

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

v2.29.8

Compare Source

Patch Changes

v2.29.7

Compare Source

Patch Changes

v2.29.6

Compare Source

Patch Changes

v2.29.5

Compare Source

Patch Changes

v2.29.4

Compare Source

Patch Changes

v2.29.3

Compare Source

Patch Changes

v2.29.2

Compare Source

Patch Changes

v2.29.1

Compare Source

Patch Changes

v2.29.0

Compare Source

Minor Changes

v2.28.1

Compare Source

Patch Changes

v2.28.0

Compare Source

Minor Changes
Patch Changes

v2.27.12

Compare Source

Patch Changes

v2.27.11

Compare Source

Patch Changes

v2.27.10

Compare Source

Patch Changes

v2.27.9

Compare Source

Patch Changes

v2.27.8

Compare Source

Patch Changes

v2.27.7

Compare Source

Patch Changes

v2.27.6

Compare Source

Patch Changes

v2.27.5

Compare Source

Patch Changes

v2.27.4

Compare Source

Patch Changes

v2.27.3

Compare Source

Patch Changes
  • #​1357 18c966a Thanks @​Andarist! - Fixed an issue with changeset status executed without since argument. It should now correctly use the configured base branch as the default value.

v2.27.2

Compare Source

Patch Changes

v2.27.1

Compare Source

Patch Changes

v2.27.0

Compare Source

Minor Changes
Patch Changes

v2.26.2

Compare Source

Patch Changes

v2.26.1

Compare Source

Patch Changes
  • #​1115 feddc88 Thanks @​Andarist! - Call pnpm publish directly from the directory of the published package. This allows pnpm to correctly handle configured publishConfig.directory.

v2.26.0

Compare Source

Minor Changes
  • #​1033 521205d Thanks @​Andarist! - A new config-level changedFilePatterns option has been added. You can configure it with an array of glob patterns like here:

    // .changeset/config.json
    {
      "changedFilePatterns": ["src/**"]
    }

    Files that do not match the configured pattern won't contribute to the "changed" status of the package to which they belong. This both affects changesets add and changeset status.

Patch Changes

v2.25.2

Compare Source

Patch Changes

[v2.25.1](https://redirect.github.com/changesets/changesets/blob/HEAD/p

❗ Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 20, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: a4550ca

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/changesets-monorepo branch from 3cd9144 to c82ae4d Compare March 3, 2026 13:45
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from c82ae4d to 2910ce0 Compare March 13, 2026 15:17
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 2910ce0 to 6f8d466 Compare April 8, 2026 14:58
@renovate renovate Bot changed the title Update changesets monorepo chore(deps): update changesets monorepo Apr 8, 2026
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 6f8d466 to a15d18e Compare April 18, 2026 00:31
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch 2 times, most recently from 54cce09 to bc9ee40 Compare May 12, 2026 10:02
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from bc9ee40 to f01511f Compare May 18, 2026 11:43
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch 2 times, most recently from 838a032 to 3ac07c0 Compare June 1, 2026 22:30
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 3ac07c0 to a1508cc Compare June 11, 2026 21:10
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch 2 times, most recently from 9dd241b to 34282e6 Compare July 16, 2026 08:58
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 34282e6 to 302c505 Compare July 30, 2026 15:03
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 302c505 to 75643fd Compare August 12, 2026 03:03
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 75643fd to 6bd0747 Compare August 26, 2026 20:59
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch 3 times, most recently from ca26481 to 9fa1542 Compare September 9, 2026 18:59
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from 9fa1542 to 22180ca Compare September 15, 2026 18:55
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch 2 times, most recently from e362c67 to c00dbca Compare October 1, 2026 11:32
@renovate
renovate Bot force-pushed the renovate/changesets-monorepo branch from c00dbca to a4550ca Compare October 5, 2026 20:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants