diff --git a/api/index.html b/api/index.html index 9404ea51..f7078269 100644 --- a/api/index.html +++ b/api/index.html @@ -1,4 +1,4 @@ - - + + diff --git a/customization.html b/customization.html index df81fa28..55ad8e8b 100644 --- a/customization.html +++ b/customization.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + @@ -277,6 +277,7 @@

- + @@ -82,7 +82,7 @@
- + diff --git a/gha.html b/gha.html index f46efa23..d2a8ea7f 100644 --- a/gha.html +++ b/gha.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + @@ -160,7 +160,7 @@

sbt-typelevel-github-actions

Usage

Add the following to your plugins.sbt:

- 
addSbtPlugin("org.typelevel" % "sbt-typelevel-github-actions" % "0.6.0")
+ 
addSbtPlugin("org.typelevel" % "sbt-typelevel-github-actions" % "0.6.1")

To use the generative functionality, run sbt githubWorkflowGenerate and commit the results. If your sbt build is ever changed such that the generated workflow is no longer in sync, the workflow run in GitHub Actions will begin failing and you will need to re-run this task (and commit the results).

General Plugin

diff --git a/index.html b/index.html index a1f9b465..d76edf35 100644 --- a/index.html +++ b/index.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + @@ -178,13 +178,13 @@

project/plugins.sbt

// Full service, batteries-included, let's go!
-addSbtPlugin("org.typelevel" % "sbt-typelevel" % "0.6.0")
+addSbtPlugin("org.typelevel" % "sbt-typelevel" % "0.6.1")
 
 // Set me up for CI release, but don't touch my scalacOptions!
-addSbtPlugin("org.typelevel" % "sbt-typelevel-ci-release" % "0.6.0")
+addSbtPlugin("org.typelevel" % "sbt-typelevel-ci-release" % "0.6.1")
 
 // Optional. Make me a website!
-addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.0")
+addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.1")

sbt-typelevel-ci-release includes all the core features mentioned above.

diff --git a/secrets.html b/secrets.html index 3c7fa29a..13711e29 100644 --- a/secrets.html +++ b/secrets.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + diff --git a/site.html b/site.html index a2c0d7dc..5dd4e947 100644 --- a/site.html +++ b/site.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + @@ -158,7 +158,7 @@

sbt-typelevel-site

Quick start

project/plugins.sbt

- 
addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.0")
+ 
addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.1")

build.sbt

// publish website from this branch
@@ -254,13 +254,13 @@ 
How can I include my project version on the website?

         
sbt-typelevel-site automatically adds VERSION and SNAPSHOT_VERSION to the mdocVariables setting
         which can be used with variable injection.

-        
For example, the sbt-typelevel VERSION is 0.6.0 and SNAPSHOT_VERSION is 0.6.0-13-6a44e1f-SNAPSHOT.

+        
For example, the sbt-typelevel VERSION is 0.6.1 and SNAPSHOT_VERSION is 0.6.1-6-1f41bce-SNAPSHOT.

         
         
How can I publish "unidoc" API docs?

         
If you generate your API documentation with sbt-unidoc,
         you can use the TypelevelUnidocPlugin to publish a Scaladoc-only artifact to Sonatype/Maven alongside your library artifacts.
         This makes it possible to browse your unidocs at javadoc.io;
-        for example, the sbt-typelevel API docs are published like this.

+        for example, the sbt-typelevel API docs are published like this.

         
// Make sure to add to your root aggregate so it gets published!
 lazy val unidocs = project
   .in(file("unidocs"))