Docouture
prerelease Prerelease 1.3.2 Latest 1.3.1 1.3.0 1.2.1 1.2.0 1.1.2 1.1.1 1.1.0 1.0.0
↑↓ navigate · ↵ select · esc close
Docouture
Docouture
prerelease Prerelease 1.3.2 Latest 1.3.1 1.3.0 1.2.1 1.2.0 1.1.2 1.1.1 1.1.0 1.0.0

v1.1.0

This release makes the docs release workflow follow a real code release on its own, and stops a single repeated link from dominating the link check. Existing sites only get the workflow changes by running docouture upgrade.

Do this

  1. Run docouture upgrade, review the diff, and commit .github/workflows/ and docs/scripts/. See CLI.

  2. Run docouture build and fix whatever it reports, then docouture doctor.

What you get

  • Docs release follows a code release. docouture-release.yml now also runs when a GitHub Release is published, so a docs release no longer needs a separate docs/release-labeled pull request merge. When the same merge carries a release-type/* label (and not skip-release), the pull request trigger backs off so the workflow does not run twice for one merge. See Releasing a documentation.

  • Version validation up front. docs/.release-version, or the manual dispatch input, is checked against the full SemVer 2.0.0 grammar before any tag is cut, instead of failing after the tag was pushed. docouture-release-preview.yml surfaces the same check as a pull request comment before merge.

  • Faster link check. The starter’s check-links script gained a timeout and per-host limiting, so a link repeated on every page, such as the repository link, no longer dominates the crawl.

check-links was removed in v1.3.0, so the last point only matters if you stay on v1.1.0 or v1.1.1.