scala-cli
scala-cli copied to clipboard
VirtusLab
Scala CLI is a command-line tool to interact with the Scala language. It lets you compile, run, test, and package your Scala code (and more!)
**What version number is to be released?** v1.3.1 **What is the estimated date for this release?** 07.05.2024 **Release procedure** Please refer to the [Release Procedure doc](https://github.com/VirtusLab/scala-cli/blob/main/.github/release/release-procedure.md). **Release notes** Please remember...
**Version(s)** Scala-Cli version: 1.2.2 Metals version: 1.3.0 Bsp version: 2.1.1 **Describe the bug** After upgrading scala-cli to version 1.2.2 the "run | debug" button has stopped showing up on VS...
**Version(s)** 1.3.0 **Describe the bug** run the command `scala-cli --power config repositories.default ''`. subsequent usages of scala-cli fail with scala.NotImplementedError **To Reproduce** ```shell scala-cli --power config repositories.default '' scala-cli repl...
**Version(s)** happens since the 1.1.1 release **Describe the bug** We are getting `RequestError` [`HttpError`] when releasing Scala CLI on `winget` with the `winget-releaser` action. ``` RequestError [HttpError]: other side closed...
**What is the problem?** Our loggers currently have comprehensive stacktrace printing and exception handling for `BuildException` only, which excludes non-build-related throwables. We should be able to handle those as well,...
Theoretically there is also an artifact for newer scala 2 versions `scala2-sbt-bridge` -> but we can do a follow up later on _Originally posted by @tgodzik in https://github.com/VirtusLab/scala-cli/pull/2873#discussion_r1579261834_
**Version(s)** 81acfafd6968d8dfc6b5e40ba9fbd3384237aa85 **Describe what needs to be done and why** Some integrations do not yet support Scala Native 0.5.x, which forces us to downgrade the default to 0.4.17 for the...
**Version(s)** 0.1.17 **Describe the bug** Passing `--python` for `run` and `repl` only makes `py` readily available without manual `import me.shadaj.scalapy.py` in some cases, in others the behaviour is identical to...
Sorry for another ticket like https://github.com/VirtusLab/scala-cli/issues/2779 / https://github.com/VirtusLab/scala-cli/issues/753... I understand there are difficulties how to handle this, but the user experience can probably still be improved. There are compiler options...
Would it possible to maintain a list of the hostnames that scala-cli tries to access? That way enterprises could consider whitelisting them too. _Originally posted by @smarter in https://github.com/VirtusLab/scala-cli/issues/2191#issuecomment-2061406905_