@zio.dev/zio-sbt 0.4.3 → 0.4.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/index.md +7 -7
  2. package/package.json +1 -1
package/index.md CHANGED
@@ -12,9 +12,9 @@ _ZIO SBT_ contains multiple sbt plugins that are useful for ZIO projects. It pro
12
12
  Add the following lines to your `plugin.sbt` file:
13
13
 
14
14
  ```scala
15
- addSbtPlugin("dev.zio" % "zio-sbt-ecosystem" % "0.4.3")
16
- addSbtPlugin("dev.zio" % "zio-sbt-ci" % "0.4.3")
17
- addSbtPlugin("dev.zio" % "zio-sbt-website" % "0.4.3")
15
+ addSbtPlugin("dev.zio" % "zio-sbt-ecosystem" % "0.4.4")
16
+ addSbtPlugin("dev.zio" % "zio-sbt-ci" % "0.4.4")
17
+ addSbtPlugin("dev.zio" % "zio-sbt-website" % "0.4.4")
18
18
  ```
19
19
 
20
20
  Then you can enable them by using the following code in your `build.sbt` file:
@@ -97,7 +97,7 @@ ZIO SBT CI plugin generates a default GitHub workflow that includes common CI ta
97
97
  To use ZIO SBT CI plugin, add the following lines to your `plugins.sbt` file:
98
98
 
99
99
  ```scala
100
- addSbtPlugin("dev.zio" % "zio-sbt-ci" % "0.4.3")
100
+ addSbtPlugin("dev.zio" % "zio-sbt-ci" % "0.4.4")
101
101
 
102
102
  resolvers ++= Resolver.sonatypeOssRepos("public")
103
103
  ```
@@ -167,12 +167,12 @@ In some cases, we may have multiple submodules in our project and we want to tes
167
167
 
168
168
  The `ciTargetScalaVersions` setting key is used to define a mapping of project names to the Scala versions that should be used for testing phase of continuous integration (CI).
169
169
 
170
- For example, suppose we have a project with the name "submoduleA" and we want to test it against Scala `2.12.20`, and for the "submoduleB" we want to test it against Scala `2.12.20` and `2.13.17` and `3.3.7`, We can define the `ciTargetScalaVersions` setting as follows:
170
+ For example, suppose we have a project with the name "submoduleA" and we want to test it against Scala `2.12.20`, and for the "submoduleB" we want to test it against Scala `2.12.20` and `2.13.18` and `3.3.7`, We can define the `ciTargetScalaVersions` setting as follows:
171
171
 
172
172
  ```scala
173
173
  ThisBuild / ciTargetScalaVersions := Map(
174
174
  "submoduleA" -> Seq("2.12.20"),
175
- "submoduleB" -> Seq("2.12.20", "2.13.17", "3.3.7")
175
+ "submoduleB" -> Seq("2.12.20", "2.13.18", "3.3.7")
176
176
  )
177
177
  ```
178
178
 
@@ -207,7 +207,7 @@ test:
207
207
  scala-project:
208
208
  - ++2.12.20 submoduleA
209
209
  - ++2.12.20 submoduleB
210
- - ++2.13.17 submoduleB
210
+ - ++2.13.18 submoduleB
211
211
  - ++3.3.7 submoduleB
212
212
  steps:
213
213
  - name: Install libuv
package/package.json CHANGED
@@ -2,5 +2,5 @@
2
2
  "name": "@zio.dev/zio-sbt",
3
3
  "description": "ZIO SBT Documentation",
4
4
  "license": "Apache-2.0",
5
- "version": "0.4.3"
5
+ "version": "0.4.4"
6
6
  }