Version Packages - #255
Merged
Merged
Version Packages#255
Conversation
unional
enabled auto-merge
September 7, 2026 05:59
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #255 +/- ##
=======================================
Coverage 94.40% 94.40%
=======================================
Files 9 9
Lines 250 250
Branches 64 64
=======================================
Hits 236 236
Misses 8 8
Partials 6 6 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@unional/fixture@6.0.0
Major Changes
fa8b087: Adopt the current majors of the first-party dependencies:
standard-log^11.5.2->^13.2.0,standard-log-color^12.0.0->^13.2.0,tersify^3.12.1->^4.0.7, andiso-error^6.0.5->^7.0.0.Why this matters to consumers. Installing
@unional/fixture@5.0.0resolvedfive majors of
type-plusand two oftersify. The oldstandard-log@11linepulls
@just-func/types@0.5.1, which still depends ontype-plus@^5.0.0, sotype-plus@5.6.0andtype-plus@6.8.1were nested under this package in everyconsumer's tree, and
tersify@3.12.1was hoisted out of it. This releaseremoves all three:
type-plusandtersifyeach resolve to a single version(
8.0.0-beta.10and4.0.7), andstandard-logto13.2.0only.Breaking.
Logger(standard-log),IsoError(iso-error) andTersible(tersify) all appear in this package's emitted.d.ts, so aconsumer's own copies of those packages must move with it.
standard-log@13also drops ES5 output.
engines.nodeis unchanged at>= 20;iso-error@7.0.0's major was that sameraise, which this package had already made.
No behaviour of
@unional/fixturechanges. The only source change is in atest:
createStandardLogForTest()moved to thestandard-log/testingsubpathin
standard-log@12.tersify@4preserves the source's own quote style ratherthan normalising to double quotes, but no assertion in this package's suite
embeds tersified function source, so no expectation moved.