From 4e5b181ffbfe2fda286ed07c966516e9348019ab Mon Sep 17 00:00:00 2001 From: Matt Travi Date: Tue, 28 Feb 2023 22:23:21 -0600 Subject: [PATCH] docs(node-version): linked to proper recipe page for ci-configurations --- docs/support/node-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/support/node-version.md b/docs/support/node-version.md index 01018a3d..ef344a89 100644 --- a/docs/support/node-version.md +++ b/docs/support/node-version.md @@ -14,7 +14,7 @@ See our [Node Support Policy](node-support-policy.md) for our long-term promise The recommended approach is to run the `semantic-release` command from a CI job running on the latest available LTS version of node. This can either be a job used by your project to test on the latest Node LTS version or a dedicated job for the release steps. -See [CI configuration](../usage/ci-configuration.md) and [CI configuration recipes](../recipes/release-workflow/README.md#ci-configurations) for more details. +See [CI configuration](../usage/ci-configuration.md) and [CI configuration recipes](../recipes/ci-configurations/README.md#ci-configurations) for more details. ## Alternative solutions