sbt-typelevel
sbt-typelevel copied to clipboard
typelevel
Let sbt work for you.
As described here: https://github.com/scalacenter/sbt-dependency-submission/blob/main/README.md#unexpected-status-403 (h/t @bpholt)
References in `ci.yml` like, e.g., `actions/setup-java@v4` are apparently to mutable tags. We could instead pin them to "known-good" versions, like `actions/setup-java@3a4f6e1af504cf6a31855fa899c6aa5355ba6c12`. As recommended by https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions.
Currently, `JobEnvironment` requires a `java.net.URL`, which seems to prevent certain usecases such as templating based on a step output - e.g. as in https://docs.github.com/en/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages. I think a variant should be...
The current [`WorkflowJob`](https://github.com/typelevel/sbt-typelevel/blob/6f9c6a5b7579d9a4569668bd7136969ad1f29013/github-actions/src/main/scala/org/typelevel/sbt/gha/WorkflowJob.scala#L19) class emphasizes 'steps' but there is another way to create job by using a [reusable workflow](https://docs.github.com/en/actions/sharing-automations/reusing-workflows#calling-a-reusable-workflow). In order to add support for reusable workflows in our current...
I notice that as of 2.13 (of cats-core), due to https://github.com/typelevel/cats/commit/c44252155c3e38ffc8201db5b43c013f2bf41d08#diff-7c156dc8732800194b79210cf462828782dcdf1b516cfc26f72afe892f8d279cR53, if you have like ``` class C extends cats.instances.AllInstances {} ``` and compile against scala 2.12, you get compilation...
So I have a project that cross-compiles to Scala 2.13 and Scala 3.X. However, the Circe model is set to only compile to Scala 2.13 because at the time Circe...
