diff --git a/api/index.html b/api/index.html index 90276ca3..7bfbe7c5 100644 --- a/api/index.html +++ b/api/index.html @@ -1,4 +1,4 @@ - - + + diff --git a/customization.html b/customization.html index 77dea891..5baad441 100644 --- a/customization.html +++ b/customization.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + diff --git a/faq.html b/faq.html index 9724fef8..cbc39b64 100644 --- a/faq.html +++ b/faq.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + diff --git a/gha.html b/gha.html index 72ffa281..28c420a7 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.2")
+ 
addSbtPlugin("org.typelevel" % "sbt-typelevel-github-actions" % "0.6.3")

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 a71f6c77..0a80e254 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.2")
+addSbtPlugin("org.typelevel" % "sbt-typelevel" % "0.6.3")
 
 // Set me up for CI release, but don't touch my scalacOptions!
-addSbtPlugin("org.typelevel" % "sbt-typelevel-ci-release" % "0.6.2")
+addSbtPlugin("org.typelevel" % "sbt-typelevel-ci-release" % "0.6.3")
 
 // Optional. Make me a website!
-addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.2")
+addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.3")

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

diff --git a/secrets.html b/secrets.html index 56b67a7c..914b13f1 100644 --- a/secrets.html +++ b/secrets.html @@ -54,7 +54,7 @@
- + @@ -82,7 +82,7 @@
- + diff --git a/site.html b/site.html index 19be23d5..3571e12d 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.2")
+ 
addSbtPlugin("org.typelevel" % "sbt-typelevel-site" % "0.6.3")

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.2 and SNAPSHOT_VERSION is 0.6.2-18-3d243b6-SNAPSHOT.

+        
For example, the sbt-typelevel VERSION is 0.6.3 and SNAPSHOT_VERSION is 0.6.3-2-8ebcebc-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"))