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
{{ message }}
This repository was archived by the owner on May 30, 2023. It is now read-only.
#1115feddc88 Thanks @Andarist! - Call pnpm publish directly from the directory of the published package. This allows pnpm to correctly handle configured publishConfig.directory.
#1033521205d Thanks @Andarist! - A new config-level changedFilePatterns option has been added. You can configure it with an array of glob patterns like here:
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.
#9974d4d67b Thanks @JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet
#9858d0115e Thanks @mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite the privatePackages.version: false setting.
#6628c08469 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
#95398d63e0 Thanks @alexamy! - Add a new line at the end of the default config file generated when invoking changeset init.
#94964585ea Thanks @Andarist, @BPScott! - Fixed the issue that caused transitive dependents of dev dependents to be bumped when a package got bumped and when using ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.updateInternalDependents: "always". To illustrate this with an example:
#858dd9b76f Thanks @dotansimha! - Added a new config flag for changesets version --snapshot mode: --snapshot-prerelease-template
#858dd9b76f Thanks @dotansimha! - Added a new config option: snapshot.prereleaseTemplate for customizing the way snapshot release numbers are being composed.
Patch Changes
#858dd9b76f Thanks @dotansimha! - A possibility to use the calculated version for snapshot releases is now stable 🥳 All snapshot-related config parameters are now grouped under a single config property called snapshot.
To migrate, make sure to update your config.json.
Old usage (still works, but comes with a deprecated warning):
#843101b1cb Thanks @caohuilin! - Fixed the printed filename in the verbose output of changeset status.
#8577febb59 Thanks @dotansimha! - Fixed an issue with dependency ranges still using pre-existing range modifiers instead of fixed package versions when performing a snapshot release. This ensures that installs of snapshot versions are always reproducible.
#74484e46d1 Thanks @mskelton! - Ignored packages are no longer listed when adding a changeset.
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
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
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.
This PR contains the following updates:
2.23.0->2.26.1Release Notes
changesets/changesets
v2.26.1Compare Source
Patch Changes
feddc88Thanks @Andarist! - Callpnpm publishdirectly from the directory of the published package. This allowspnpmto correctly handle configuredpublishConfig.directory.v2.26.0Compare Source
Minor Changes
#1033
521205dThanks @Andarist! - A new config-levelchangedFilePatternsoption has been added. You can configure it with an array of glob patterns like here: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 addandchangeset status.Patch Changes
598136a,521205d,521205d,598136a,598136a,521205d]:v2.25.2Compare Source
Patch Changes
6cc4300]:v2.25.1Compare Source
Patch Changes
#997
4d4d67bThanks @JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet#985
8d0115eThanks @mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite theprivatePackages.version: falsesetting.v2.25.0Compare Source
Minor Changes
#662
8c08469Thanks @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
#953
98d63e0Thanks @alexamy! - Add a new line at the end of the default config file generated when invokingchangeset init.#949
64585eaThanks @Andarist, @BPScott! - Fixed the issue that caused transitive dependents of dev dependents to be bumped when a package got bumped and when using___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.updateInternalDependents: "always". To illustrate this with an example:With a changeset for
pkg-athepkg-ccould have been sometimes incorrectly released.Updated dependencies [
8c08469,8c08469,64585ea]:v2.24.4Compare Source
Patch Changes
c140171]:v2.24.3Compare Source
Patch Changes
b023e4b]:v2.24.2Compare Source
Patch Changes
#900
7d998eeThanks @sdirosa! - Fixed an issue with generating changelogs not being skipped when thechangelogconfig option was set tofalse.#720
0fd56e1Thanks @bhovhannes! - Private packages without aversionfield are no longer listed when adding a changeset.#844
8627ec1Thanks @Andarist! - Attempt to logstdoutwhen publish fails ifstderris empty and JSON error can't be retrieved from none of those.Updated dependencies [
7d998ee,7d998ee]:v2.24.1Compare Source
Patch Changes
f64bc1b]:v2.24.0Compare Source
Minor Changes
#858
dd9b76fThanks @dotansimha! - Added a new config flag forchangesets version --snapshotmode:--snapshot-prerelease-template#858
dd9b76fThanks @dotansimha! - Added a new config option:snapshot.prereleaseTemplatefor customizing the way snapshot release numbers are being composed.Patch Changes
#858
dd9b76fThanks @dotansimha! - A possibility to use the calculated version for snapshot releases is now stable 🥳 All snapshot-related config parameters are now grouped under a single config property calledsnapshot.To migrate, make sure to update your
config.json.Old usage (still works, but comes with a deprecated warning):
{ "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": { "useCalculatedVersionForSnapshots": true } }New usage:
{ "snapshot": { "useCalculatedVersion": true } }Updated dependencies [
dd9b76f,dd9b76f,dd9b76f]:v2.23.2Compare Source
Patch Changes
e174172Thanks @NicoKam! - Fixed filtering of the ignored packages when adding a changeset.v2.23.1Compare Source
Patch Changes
#843
101b1cbThanks @caohuilin! - Fixed the printed filename in the verbose output ofchangeset status.#857
7febb59Thanks @dotansimha! - Fixed an issue with dependency ranges still using pre-existing range modifiers instead of fixed package versions when performing a snapshot release. This ensures that installs of snapshot versions are always reproducible.#744
84e46d1Thanks @mskelton! - Ignored packages are no longer listed when adding a changeset.Updated dependencies [
2827c7a,7b1c0c1,7febb59]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.