Conversation
🦋 Changeset detectedLatest commit: 05af694 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #1494 +/- ##
=======================================
Coverage ? 80.82%
=======================================
Files ? 53
Lines ? 2216
Branches ? 656
=======================================
Hits ? 1791
Misses ? 421
Partials ? 4 ☔ View full report in Codecov by Sentry. |
I thought it could affect it in a sense that it would no longer be able to read those old changeset files. This is an integration and the user can't chose to use a bot compatible with old changesets as that bot is updated out of their control. Now, when looking through its code... I'm not sure if it handles that at all today: It might be able to read them (nested But either way, that bot doesn't use |
This removes support for changeset in v1 format in the
.changesetdirectory.The previous warning mentions that it'll error instead of completely not supporting it (like in this PR), I don't know if we need to keep that behaviour though. It already feels like a long time ago.
At #1473, there's a mention about this change that could affect https://github.com/changesets/bot, however I can't tell how this affects that repo when reading the source.