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

Update dependency @changesets/cli to ^2.27.11 #9

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

Conversation

mend-5034428[bot]
Copy link

@mend-5034428 mend-5034428 bot commented Oct 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) ^2.20.0 -> ^2.27.11 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

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

Configuration

📅 Schedule: 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.

🔕 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

@mend-5034428 mend-5034428 bot force-pushed the whitesource-remediate/changesets-cli-2.x branch from cff37c6 to 1616e34 Compare November 21, 2024 06:09
@mend-5034428 mend-5034428 bot changed the title Update dependency @changesets/cli to ^2.27.9 Update dependency @changesets/cli to ^2.27.10 Nov 21, 2024
@mend-5034428 mend-5034428 bot force-pushed the whitesource-remediate/changesets-cli-2.x branch from 1616e34 to 995dc6e Compare December 18, 2024 10:56
@mend-5034428 mend-5034428 bot changed the title Update dependency @changesets/cli to ^2.27.10 Update dependency @changesets/cli to ^2.27.11 Dec 18, 2024
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