Update website to point to latest stable release

build.sbt

@@ -330,7 +330,8 @@ lazy val docs = project
       (ThisBuild / baseDirectory).value / "website" / "target" / "docs",
     mdocExtraArguments := List("--no-link-hygiene"),
     mdocVariables := Map(
-      "VERSION" -> version.value.replaceFirst("\\+.*", "")
+      "VERSION" -> version.value.replaceFirst("\\+.*", ""),
+      "STABLE_VERSION" -> "0.7.29"
     ),
     fork := false
   )

docs/fixtures.md

@@ -181,6 +181,8 @@ class MySuite extends munit.FunSuite {
 
 ## Asynchronous fixtures with `FutureFixture`
 
+> This feature is only available in the latest unstable version @VERSION@
+
 Extend `FutureFixture[T]` to return `Future[T]` values from the lifecycle
 methods `beforeAll`, `beforeEach`, `afterEach` and `afterAll`.
 
@@ -218,6 +220,8 @@ class AsyncFilesSuite extends FunSuite {
 
 ## Asynchronous fixtures with custom effect type
 
+> This feature is only available in the latest unstable version @VERSION@
+
 First, create a new `EffectFixture[T]` class that extends `munit.AnyFixture[T]`
 and overrides all lifecycle methods to return values of type `Effect[Unit]`. For
 example:

docs/getting-started.md

@@ -24,7 +24,7 @@ MUnit is a Scala testing library with the following goals:
 **sbt:**
 
 ```scala
-libraryDependencies += "org.scalameta" %% "munit" % "@VERSION@" % Test
+libraryDependencies += "org.scalameta" %% "munit" % "@STABLE_VERSION@" % Test
 // Use %%% for non-JVM projects.
 ```
 

docs/integrations/scalacheck.md

@@ -12,7 +12,7 @@ ScalaCheck support is provided as a separate module. You can add it to your
 build via:
 
 ```scala
-libraryDependencies += "org.scalameta" %% "munit-scalacheck" % "@VERSION@" % Test
+libraryDependencies += "org.scalameta" %% "munit-scalacheck" % "@STABLE_VERSION@" % Test
 ```
 
 You can then extend `ScalaCheckSuite` and write ScalaCheck property tests:

docs/tests.md

@@ -115,9 +115,10 @@ class CustomTimeoutSuite extends munit.FunSuite {
 }
 ```
 
-Note that old version for MUnit (v0.x series) the timeout only applied to async
-tests. Since the release of MUnit v1.0, the timeout applies to all tests
-including non-async tests.
+> Note that `munitTimeout` is only respected for async tests in the stable
+> version version of MUnit (v0.x series). The setting is ignored by normal
+> non-async tests. However, starting with MUnit v1.0 (latest milestone release:
+> @VERSION@), the timeout applies to all tests including non-async tests.
 
 ## Run tests in parallel