Skip to content

Extract library versions into vals in build.mill#87

Draft
kubukoz wants to merge 1 commit into
mainfrom
extract-version-vals
Draft

Extract library versions into vals in build.mill#87
kubukoz wants to merge 1 commit into
mainfrom
extract-version-vals

Conversation

@kubukoz

@kubukoz kubukoz commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Pull every library version literal in build.mill up into a top-level val and reference it via interpolation.
  • Pre-existing version bumps already on disk (e.g. lsp-smithy-definitions:0.3.0, bsp4s:0.7.0, jsonrpcVersion 0.2.0, smithy4s plugin 0.19.7) are kept verbatim — only the indirection changes.
  • testModule's Scala version (3.7.4) is also lifted into a val for consistency.

Build status

  • lsp-smithy-definitions:0.3.0 resolves now (it was published during this session — initial failure was due to the artifact not yet being on Maven Central).
  • However, compile is still failing with 20 errors in sls/ (DiagnosticManager, MessageTracer, ServerImpl) because the bumped upstream libraries changed their APIs (e.g. lsp.SignatureHelp is no longer wrapped in Option, List[lsp.Location] no longer accepts None, etc.).
  • Adapting the source to the new APIs is out of scope for this PR — this is a pure build.mill refactor.

Test plan

  • ./mill __.compile — blocked on a separate follow-up to adapt sls/ sources to new lsp-smithy-definitions / jsonrpclib / bsp4s APIs
  • ./mill _.test — blocked on the above

🤖 Generated with Claude Code

Why: avoid duplicating version literals across modules and make bumps
easier to spot/coordinate. Pre-existing version bumps (e.g.
lsp-smithy-definitions 0.3.0, bsp4s 0.7.0, jsonrpc 0.2.0) are kept as-is
and referenced by val.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant