-
Notifications
You must be signed in to change notification settings - Fork 7
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 all non-major dependencies #27
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/all-minor-patch
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 10, 2021 01:00
e6a3f18
to
ceafb62
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #27 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 15 15
Branches 3 3
=========================================
Hits 15 15 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 22, 2021 11:55
ceafb62
to
41fc85c
Compare
renovate
bot
changed the title
chore(deps): update dependency nuxt to ^2.14.12
chore(deps): update all non-major dependencies
Jan 22, 2021
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 31, 2021 21:57
41fc85c
to
42da6a0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
February 15, 2021 13:17
421769f
to
b237f4e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
February 23, 2021 10:18
4292969
to
c9cd26d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 2, 2021 11:53
c9cd26d
to
59ca63c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 26, 2021 13:09
59ca63c
to
9d24fb4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
May 15, 2021 20:45
e091383
to
de484b9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 15, 2021 09:08
de484b9
to
5ba8c64
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 19, 2021 00:58
5ba8c64
to
c6a7535
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 7, 2022 10:11
c6a7535
to
395002e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 26, 2022 12:30
395002e
to
614cd06
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 25, 2022 01:29
614cd06
to
6291828
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 18, 2022 15:56
6291828
to
60825fa
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 25, 2022 18:00
60825fa
to
e93325a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 20, 2022 09:31
e93325a
to
71b785f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 17, 2023 16:09
71b785f
to
f22f555
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 24, 2023 22:03
f22f555
to
e1269ef
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 9, 2023 21:59
e1269ef
to
97eec8e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 27, 2023 11:52
97eec8e
to
300e306
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
July 15, 2023 00:34
300e306
to
c21be11
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 24, 2023 03:19
c21be11
to
3cbf95b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 28, 2023 07:28
3cbf95b
to
0cbabfb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 28, 2023 12:03
0cbabfb
to
0227b08
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 12, 2024 16:38
0227b08
to
62bb2d7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
May 20, 2024 15:59
d562f0b
to
2c90ec2
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
July 4, 2024 23:47
2c90ec2
to
3282744
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 4, 2024 14:26
3282744
to
aab4951
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 16, 2024 14:39
aab4951
to
cf1e518
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 3, 2024 16:53
cf1e518
to
4b09af6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 20, 2024 11:16
4b09af6
to
38e2aac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.12.0
->^2.27.10
^0.8.2
->^0.11.1
^1.2.4
->^1.4.0
^8.2.2
->^8.4.1
^2.14.11
->^2.18.1
Release Notes
changesets/changesets (@changesets/cli)
v2.27.10
Compare Source
v2.27.9
Compare Source
Patch Changes
#1458
400ab7b
Thanks @benmccann! - Moved@types/semver
todevDependencies
#1462
689e541
Thanks @benmccann! - removeoutdent
dependencyv2.27.8
Compare Source
v2.27.7
Compare Source
Patch Changes
#1047
d108fa6
Thanks @patzick! - Fixed a crash that could occur when depending on a tagged version of another workspace package.#1400
dd6e5bb
Thanks @Andarist! - Fixed a crash that prevented the CLI from running in a scenario when a workspace depends on the root workspaceUpdated dependencies [
d108fa6
,dd6e5bb
,dd6e5bb
]:v2.27.6
Compare Source
Patch Changes
#1392
f295b3e
Thanks @bluwy! - Replacemeow
dependency withmri
to reduce the number of transitive dependencies#1390
6a3452e
Thanks @bluwy! - Displaychangeset status --verbose
in list form and removetty-table
dependencyv2.27.5
Compare Source
Patch Changes
#1370
5e9d33a
Thanks @Andarist! - Fixed a regression that causedchangeset version
to fail on packages having a dev dependency on a skipped package.Updated dependencies [
5e9d33a
]:v2.27.4
Compare Source
Patch Changes
#1361
954a16a
Thanks @jakebailey! - Ensure thatversion
/tag
do not touch private packages with when versioning/tagging is turned off usingversionPackages
config#1369
d729d8c
Thanks @Andarist! -changeset tag
should now correctly skip tags that exist on the remoteUpdated dependencies [
954a16a
]:v2.27.3
Compare Source
Patch Changes
18c966a
Thanks @Andarist! - Fixed an issue withchangeset status
executed withoutsince
argument. It should now correctly use the configured base branch as the default value.v2.27.2
Compare Source
Patch Changes
#1354
69be7dc
Thanks @Andarist! - Fixed an issue withchangeset status
incorrectly returning an error status in two cases:privatePackage.version
was set tofalse
#1351
c6da182
Thanks @TheHolyWaffle! - Fix an issue with not applying a custom.prettierrc
configuration withprettier@>= 3.1.1
Updated dependencies [
c6da182
]:v2.27.1
Compare Source
Patch Changes
86cfff1
Thanks @Andarist! - Make./bin.js
available throughpackage.json#exports
to fix compatibility withchangesets/action
.v2.27.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.#1236
dfd4cca
Thanks @camertron! - Avoid using short commit IDsPatch Changes
#1053
90a870a
Thanks @paescuj! - Replace the dependencyis-ci
withci-info
.Updated dependencies [
a971652
,dfd4cca
]:v2.26.2
Compare Source
Patch Changes
#1176
41988ce
Thanks @joshwooding! - Bumpsemver
dependency to v7.5.3Updated dependencies [
41988ce
]:v2.26.1
Compare Source
Patch Changes
feddc88
Thanks @Andarist! - Callpnpm publish
directly from the directory of the published package. This allowspnpm
to correctly handle configuredpublishConfig.directory
.v2.26.0
Compare Source
Minor Changes
#1033
521205d
Thanks @Andarist! - A new config-levelchangedFilePatterns
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
andchangeset status
.Patch Changes
598136a
,521205d
,521205d
,598136a
,598136a
,521205d
]:v2.25.2
Compare Source
Patch Changes
6cc4300
]: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 theprivatePackages.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
#953
98d63e0
Thanks @alexamy! - Add a new line at the end of the default config file generated when invokingchangeset init
.#949
64585ea
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:With a changeset for
pkg-a
thepkg-c
could have been sometimes incorrectly released.Updated dependencies [
8c08469
,8c08469
,64585ea
]:v2.24.4
Compare Source
Patch Changes
c140171
]:v2.24.3
Compare Source
Patch Changes
b023e4b
]:v2.24.2
Compare Source
Patch Changes
#900
7d998ee
Thanks @sdirosa! - Fixed an issue with generating changelogs not being skipped when thechangelog
config option was set tofalse
.#720
0fd56e1
Thanks @bhovhannes! - Private packages without aversion
field are no longer listed when adding a changeset.#844
8627ec1
Thanks @Andarist! - Attempt to logstdout
when publish fails ifstderr
is empty and JSON error can't be retrieved from none of those.Updated dependencies [
7d998ee
,7d998ee
]:v2.24.1
Compare Source
Patch Changes
f64bc1b
]:v2.24.0
Compare Source
Minor Changes
#858
dd9b76f
Thanks @dotansimha! - Added a new config flag forchangesets 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
#858
dd9b76f
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 calledsnapshot
.To migrate, make sure to update your
config.json
.Old usage (still works, but comes with a deprecated warning):
New usage:
Updated dependencies [
dd9b76f
,dd9b76f
,dd9b76f
]:v2.23.2
Compare Source
Patch Changes
e174172
Thanks @NicoKam! - Fixed filtering of the ignored packages when adding a changeset.v2.23.1
Compare Source
Patch Changes
#843
101b1cb
Thanks @caohuilin! - Fixed the printed filename in the verbose output ofchangeset status
.#857
7febb59
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.#744
84e46d1
Thanks @mskelton! - Ignored packages are no longer listed when adding a changeset.Updated dependencies [
2827c7a
,7b1c0c1
,7febb59
]:v2.23.0
Compare Source
Minor Changes
745b771
Thanks @JakeGinnivan! - Upgradedtty-table
to fix deprecation warnings coming from its transitive dependency.Patch Changes
#811
c54c25d
Thanks @samrose3! - Improved accessibility of the CLI prompts by using selected/unselected indicators that don't rely solely on the colors.#767
d6bfcc5
Thanks @Andarist! - Improve the error message when a package referenced in a changeset can't be found. The message will now also include the changeset's ID.Updated dependencies [
d6bfcc5
]:v2.22.0
Compare Source
Minor Changes
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 containgetAddMessage
and/orgetVersionMessage
. This allows you to configure how the commit message is generated, if[skip ci]
gets included, etc.Patch Changes
#776
ad7506d
Thanks @janosh! -changeset init
will now configurebaseBranch: "main"
in the.changeset/config.json
as the default value.#770
eb86652
Thanks @alizeait! -changeset add
andchangeset status
should now properly handle the situation where Changesets are managed from a directory different than the root of the repository.Updated dependencies [
c87eba6
,eb86652
,c87eba6
,c87eba6
]:v2.21.1
Compare Source
Patch Changes
#760
5a2a59a
Thanks @Andarist! - Fixed an issue with logging non-stringified Buffers in case of publish errors.#769
3e8e672
Thanks @Andarist! - Fixed an infinite loop involving a fixed group of packages and a package within that group that was both ignored and dependent on another package from that group.Updated dependencies [
3e8e672
]: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
#706
0812858
Thanks @Andarist! - Fixed an issue with"none"
releases causing package versions being bumped during snapshot releases. In addition to when you create"none"
release types explicitly Changesets might create them implicitly in some situations, for example under some circumstances this issue caused snapshot releases to be created sometimes for ignored packages.#703
15c461d
Thanks @Andarist! - Fixed an issue with*
dependency ranges not being replaced in premode. Those have to replaced with exact versions because prereleases don't satisfy wildcard ranges. A published prerelease package with such dependency range left untouched won't install correct prerelease dependency version.#749
d14cf79
Thanks @Andarist! - Fixed an issue that caused created CHANGELOG files not being formatted in the same way as the updated ones (this could happen when callingchangeset version
for the very first time for a package).#751
59c7ebc
Thanks @Rugvip! - Fixed an issue where dependent packages would sometimes not get bumped properly when exiting prerelease mode.#703
15c461d
Thanks @Andarist! - Fixed an issue with dependant packages being always bumped when their*
dependency was bumped.Updated dependencies [
0812858
,15c461d
,27a5a82
,27a5a82
,d14cf79
,27a5a82
,0d1debd
,59c7ebc
,15c461d
]: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
#740
957e39c
Thanks @akphi! - Fixed an issue with failing to parse changesets containing a completely empty summary.#693
1be201f
Thanks @luciaquirke! - Fixed an issue withnone
release type sometimes overriding other release types and thus preventing a release from happening.Updated dependencies [
6f9c9d6
,77c1cef
,1be201f
]:v2.19.0
Compare Source
Minor Changes
b9b6453
Thanks @Andarist! - Added support for a--no-git-tag
CLI flag that can be used withchangeset publish
to skip creating git tags for published packages. This is mostly useful when publishing snapshot releases.Patch Changes
#713
82be80e
Thanks @zthxxx! - Fixed an issue with not being able to reenter exited pre mode.#708
ab8f2b2
Thanks @Andarist! - Updatedis-ci
dependency that helps us to check if Changesets are executed in the CI environment.#710
4272cb0
Thanks @Andarist! - Errors received fromnpm profile get --json
, that is used to check if 2FA is required, will now always be printed.Updated dependencies [
82be80e
,e4c4b29
]:v2.18.1
Compare Source
Patch Changes
#676
d8f0e68
Thanks @Andarist! - Improved compatibility with npm 7+ since they've started to print errors to thestderr
(where previously they were printed tostdout
) when usingnpm publish --json
.#676
d8f0e68
Thanks @Andarist! - Fixed an internal issue that preventednpm publish --json
's output to be handled properly. This makes sure that unrelated JSONs printed by lifecycle scripts don't interfere with our logic.[#667](https://redirect.github.com/atlassi
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.