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
Describe the bug
When running scala-cli publish setup --ci on a new Scala CLI project, it seems it tries to download binaries from scala-cli/scala-cli-signing, and fails, as these seem to now live in VirtusLab/scala-cli-signing.
To Reproduce
On a new project, run scala-cli publish setup --ci </dev/null. It should print lines like
Version(s)
1.0.0-RC1
Describe the bug
When running
scala-cli publish setup --ci
on a new Scala CLI project, it seems it tries to download binaries from scala-cli/scala-cli-signing, and fails, as these seem to now live in VirtusLab/scala-cli-signing.To Reproduce
On a new project, run
scala-cli publish setup --ci </dev/null
. It should print lines like(Note that the
Downloaded
from the coursier logger is misleading, the download actually failed.)Expected behaviour
Scala CLI should download scala-cli-signing binaries from VirtusLab/scala-cli-signing for scala-cli-signing versions >=
0.1.15
(and keep using scala-cli/scala-cli-signing for lower versions).The text was updated successfully, but these errors were encountered: