sbt-typelevel
sbt-typelevel copied to clipboard
typelevel
Let sbt work for you.
Hopefully a future version of 2.13 will resolve scala/bug#13128. When that happens, we should revisit the patch range: https://github.com/typelevel/sbt-typelevel/blob/17a4562a1daf521b33876f84a290d86556f49bf0/settings/src/main/scala/org/typelevel/sbt/TypelevelSettingsPlugin.scala#L211-L214
Related to https://github.com/scala/scala3/issues/22890 Since 3.7.0 we've discovered cases in the ecosystem where 2 different versions of `scala3-library` where present on the classpath. Previously it was not an issue, as these...
Created a new types - `Workflow`: Represents an entire workflow file, like `ci.yml` and `clean.yml` - `Secrets`: How secrets in a job should be handled by called workflows. - `WorkflowTrigger`:...
## About this PR š¦ Updates [com.github.sbt:sbt-unidoc](https://github.com/sbt/sbt-unidoc) from `0.5.0` to `0.6.0` š [GitHub Release Notes](https://github.com/sbt/sbt-unidoc/releases/tag/v0.6.0) - [Version Diff](https://github.com/sbt/sbt-unidoc/compare/v0.5.0...v0.6.0) ## Usage ā **Please merge!** I'll automatically update this PR to resolve...
![typelevel-steward[bot] avatar](https://avatars.githubusercontent.com/u/3731824?v=4 "typelevel-steward[bot] avatar"){kind=avatar}
One might argue that users can use `githubWorkflowPublishCond` to prevent publishing from forked repos. Sure, but Iām confident this condition should be the default. Adding it manually to the build...
## About this PR š¦ Updates org.yaml:snakeyaml from `1.33` to `2.5` ## Usage ā **Please merge!** I'll automatically update this PR to resolve conflicts as long as you don't change...
I want to define this trigger in my workflow: ```yaml on: push: branches: - main pull_request: types: [synchronize, opened, reopened] ``` Which will run a build on my main branch,...
Scala 3.7 flags more unused implicit and explicit values as warnings. In some cases, this is intended on our part and we will need to annotate them with the `@nowarn`...
Is there a way to set `tlVersionIntroduced` for a subproject in a multi-project build? My use case is that I'm adding a new subproject to a multi-project, which causes `versionPolicyFindDependencyIssues`...
