You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`just test-snippets` derived the chimney version with an unfiltered
`$(sbt -batch -error 'print chimney/version')`. Under sbt 2.x `-error` no longer
suppresses the terminal control output, so that captured the version PLUS leaked
ANSI escapes (`\e[0J`) and a trailing `[success] elapsed time` line - a polluted
string that broke scala-cli dependency resolution and thus every snippet.
Query with a non-client sbt, strip ANSI, then grep the version out (and guard for
empty), and publish with `sbt --client`. This mirrors how kindlings/hearth solved
the same issue. Keep the sbt call and the grep pipeline as separate `|| true`
statements so `set -euo pipefail` can't abort on a grep no-match / head SIGPIPE.
Verified locally on sbt 2.0.2: version resolves to a clean
`2.0.0-M4-1-gca22d63-SNAPSHOT` and all documentation snippets pass.
0 commit comments