Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @changesets/cli to v2.27.5 #87

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) 2.17.0 -> 2.27.5 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

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
  • #​1267 86cfff1 Thanks @​Andarist! - Make ./bin.js available through package.json#exports to fix compatibility with changesets/action.

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

Compare Source

Patch Changes
  • #​997 4d4d67b Thanks @​JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet

  • #​985 8d0115e Thanks @​mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite the privatePackages.version: false setting.

v2.25.0

Compare Source

Minor Changes
  • #​662 8c08469 Thanks @​JakeGinnivan! - Private packages can now be tagged in the same way public packages do when they are published to npm.

    To enable set privatePackages: { version: true, tag: true } in your config.json.

    You can also now opt private packages out of versioning entirely by setting privatePackages: false.

Patch Changes

v2.24.4

Compare Source

Patch Changes

v2.24.3

Compare Source

Patch Changes

v2.24.2

Compare Source

Patch Changes

v2.24.1

Compare Source

Patch Changes

v2.24.0

Compare Source

Minor Changes
  • #​858 dd9b76f Thanks @​dotansimha! - Added a new config flag for changesets version --snapshot mode: --snapshot-prerelease-template

  • #​858 dd9b76f Thanks @​dotansimha! - Added a new config option: snapshot.prereleaseTemplate for customizing the way snapshot release numbers are being composed.

Patch Changes

v2.23.2

Compare Source

Patch Changes

v2.23.1

Compare Source

Patch Changes

v2.23.0

Compare Source

Minor Changes
Patch Changes

v2.22.0

Compare Source

Minor Changes
  • #​768 c87eba6 Thanks @​rohit-gohri! - Allow "commit" option to be more configurable. You can now point to a module (using a module name or a relative path) that might contain getAddMessage and/or getVersionMessage. This allows you to configure how the commit message is generated, if [skip ci] gets included, etc.
Patch Changes

v2.21.1

Compare Source

Patch Changes

v2.21.0

Compare Source

Minor Changes
  • #​690 27a5a82 Thanks @​Andarist! - Added a new .changeset/config.json option: fixed. It can be used to group packages that should always be released together. If any package from a group is going to be released then all packages from that group will be released together (with the same version).

    This is similar to what people often know from Lerna as this is how their fixed/locked mode works.

Patch Changes

v2.20.0

Compare Source

Minor Changes
  • #​698 9e14a9a Thanks @​zthxxx! - Reworked the CLI output when adding a changeset. This includes fixing broken formatting in certain terminal width, reducing visual noise and making other small adjustments.

  • #​704 6f9c9d6 Thanks @​Andarist! - Dependencies specified using a tag will no longer result in printing incorrect errors in the console.

Patch Changes

v2.19.0

Compare Source

Minor Changes
  • #​701 b9b6453 Thanks @​Andarist! - Added support for a --no-git-tag CLI flag that can be used with changeset publish to skip creating git tags for published packages. This is mostly useful when publishing snapshot releases.
Patch Changes

v2.18.1

Compare Source

Patch Changes

v2.18.0

Compare Source

Minor Changes
  • #​634 2b49c39 Thanks @​joeldenning! - The new changeset tag command has been added. It can be used to create git tags for all packages.

    This is helpful in situations where a different tool is used to publish packages instead of Changesets. For situations where changeset publish is executed, running changeset tag is not needed.

    Note that it is expected that changeset version is run before changeset tag, so that the package.json versions are updated before the git tags are created. This command also doesn't take any configuration into account - it simply create tags for all packages with whatever version that is currently in their respective package.json.

Patch Changes

Configuration

📅 Schedule: Branch creation - "before 6:00am on the first day of the month" in timezone UTC, 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 1, 2023
@changeset-bot
Copy link

changeset-bot bot commented Jun 1, 2023

⚠️ No Changeset found

Latest commit: eaef05a

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 changed the title chore(deps): update dependency @changesets/cli to v2.26.1 chore(deps): update dependency @changesets/cli to v2.26.2 Jun 27, 2023
@renovate renovate bot force-pushed the renovate/changesets-cli-2.x branch from 492b209 to ddac4fe Compare June 27, 2023 11:02
@renovate renovate bot changed the title chore(deps): update dependency @changesets/cli to v2.26.2 chore(deps): update dependency @changesets/cli to v2.27.0 Nov 28, 2023
@renovate renovate bot force-pushed the renovate/changesets-cli-2.x branch 2 times, most recently from 99e2132 to c3ed619 Compare November 28, 2023 13:41
@renovate renovate bot changed the title chore(deps): update dependency @changesets/cli to v2.27.0 chore(deps): update dependency @changesets/cli to v2.27.1 Nov 28, 2023
@renovate renovate bot force-pushed the renovate/changesets-cli-2.x branch from c3ed619 to 9f0ef6d Compare May 17, 2024 17:09
@renovate renovate bot changed the title chore(deps): update dependency @changesets/cli to v2.27.1 chore(deps): update dependency @changesets/cli to v2.27.2 May 17, 2024
@renovate renovate bot force-pushed the renovate/changesets-cli-2.x branch from 9f0ef6d to 70efc39 Compare May 20, 2024 09:04
@renovate renovate bot changed the title chore(deps): update dependency @changesets/cli to v2.27.2 chore(deps): update dependency @changesets/cli to v2.27.3 May 20, 2024
@renovate renovate bot force-pushed the renovate/changesets-cli-2.x branch from 70efc39 to 709b8fd Compare May 28, 2024 12:42
@renovate renovate bot changed the title chore(deps): update dependency @changesets/cli to v2.27.3 chore(deps): update dependency @changesets/cli to v2.27.4 May 28, 2024
@renovate renovate bot force-pushed the renovate/changesets-cli-2.x branch from 709b8fd to eaef05a Compare May 28, 2024 16:47
@renovate renovate bot changed the title chore(deps): update dependency @changesets/cli to v2.27.4 chore(deps): update dependency @changesets/cli to v2.27.5 May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants