Skip to content

Fix Scala 3 coverage documentation link - #833

Merged
tgodzik merged 1 commit into
scoverage:mainfrom
anatoliykmetyuk:br/fix-scala3-coverage-doc-link
Nov 4, 2026
Merged

tgodzik merged 1 commit into
scoverage:mainfrom
anatoliykmetyuk:br/fix-scala3-coverage-doc-link

Conversation

@anatoliykmetyuk

Copy link
Copy Markdown
Contributor

3.3_LTS seems to be a symlink that resolves to the current LTS in the docs, and for whatever reason seems broken in this documentation path. Hard-coding the version to workaround.

Comment thread README.md Outdated
**NOTE**: That this repository contains the Scala compiler plugin for Code coverage
in Scala 2 and other coverage utilities for generating reports. For Scala 3 code
coverage the [compiler](https://github.com/lampepfl/dotty) natively [produces](https://www.scala-lang.org/api/3.3_LTS/docs/docs/internals/coverage.html)
coverage the [compiler](https://github.com/lampepfl/dotty) natively [produces](https://www.scala-lang.org/api/3.4.1/docs/docs/internals/coverage.html)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why 3.4.1 though, that's an unsupported version

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, as suggested by scala/scala-lang#1966 (comment)

@anatoliykmetyuk
anatoliykmetyuk force-pushed the br/fix-scala3-coverage-doc-link branch from ecf46a5 to e34182e Compare November 4, 2026 06:50

@tgodzik tgodzik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@tgodzik
tgodzik merged commit 683d86b into scoverage:main Nov 4, 2026
51 checks passed
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.

2 participants