Release prep for v0.3.0: latest-yields conflict semantics and scalafmt - #28
Merged
Conversation
dependencyPairs compared specifiers by string equality, and a missing version resolves to "latest" — so one unversioned dep in any published library hard-conflicted with every consumer that pins a version, reachable through transitive classpath manifests rather than the consumer's own build file, escapable only via npmOverrides. "latest" is only the placeholder for an unversioned declaration, so any explicit specifier now wins over it. Two different explicit specifiers (including semantically overlapping ones like ^19 and ^19.0.0) still fail deterministically, and the conflict message no longer lists the irrelevant "latest". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Deliberately conservative: Scala 3 dialect, maxColumn 120, newlines.source = keep, and no brace/indentation conversion — the tree legitimately mixes both styles, and this config normalizes spacing and wrapping without re-styling it. The one-time reformat touched 10 files (+49/-26). CI checks formatting ahead of compilation on every platform so it cannot drift. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GitHub's Windows runners default to autocrlf=true, which rewrote every Scala source to CRLF at checkout — scalafmt then reported all 28 files misformatted. .gitattributes now checks sources out as LF on every platform; batch files stay CRLF because cmd.exe mis-parses some constructs without it (their blobs are still stored normalized, which is the one renormalization in this commit). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The two pre-tag items for v0.3.0, per the release plan.
latestyields to explicit specifiersdependencyPairscompared specifiers by string equality, and a missing version resolves tolatest— so one unversioned dep in any published library hard-conflicted with every consumerthat pins a version, reachable through transitive classpath manifests rather than the consumer's
own build file. An explicit specifier now wins over
latest; two different explicitspecifiers (even semantically overlapping ones like
^19vs^19.0.0) still faildeterministically, and the conflict message no longer lists the irrelevant
latest. Unit testscover both directions, order independence, and the only-unversioned case; README, CHANGELOG, and
MIGRATING-0.3 updated.
scalafmt
.scalafmt.conf(deliberately conservative: Scala 3 dialect,maxColumn = 120,newlines.source = keep, no brace/indentation conversion — the tree legitimately mixes bothstyles) plus a
checkFormatAllstep in CI ahead of compilation. The one-time reformat touched10 files, +49/−26 — the tree was already near-consistent, and the config is chosen to keep it
that way rather than to re-style it.
Full suites green. After this merges,
mainis tag-ready forv0.3.0.