From 5f1b68c8de492dd9d7c54681054a2f7f0946246a Mon Sep 17 00:00:00 2001 From: timedout Date: Tue, 14 Jul 2026 04:52:09 +0100 Subject: [PATCH] fix: list indentation --- docs/development/releasing.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/development/releasing.mdx b/docs/development/releasing.mdx index 183785436..28a4eae35 100644 --- a/docs/development/releasing.mdx +++ b/docs/development/releasing.mdx @@ -28,13 +28,13 @@ This means a release timeline MIGHT look like: - Week 2: New major features & other changes - Week 3: New minor features & bugfixing - Week 4: Release candidates and final release -- Day 1: Fork release branch from `main` and tag `YY.MM.0-rc.1` -- Day 2: If there are bugfixes, tag `YY.MM.0-rc.2` -- Day 3: If there are bugfixes, tag `YY.MM.0-rc.3` -- Day 4: If there are bugfixes, tag `YY.MM.0-rc.4` -- Day 5: If there are bugfixes, tag `YY.MM.0-rc.5` -- Day 6: If there are bugfixes, tag `YY.MM.0-rc.6` -- Day 7: If there are no serious bugs, tag `YY.MM.0` and release. + - Day 1: Fork release branch from `main` and tag `YY.MM.0-rc.1` + - Day 2: If there are bugfixes, tag `YY.MM.0-rc.2` + - Day 3: If there are bugfixes, tag `YY.MM.0-rc.3` + - Day 4: If there are bugfixes, tag `YY.MM.0-rc.4` + - Day 5: If there are bugfixes, tag `YY.MM.0-rc.5` + - Day 6: If there are bugfixes, tag `YY.MM.0-rc.6` + - Day 7: If there are no serious bugs, tag `YY.MM.0` and release. New changes of any sort may be made to the `main` branch at any point during the month, but they will not be included in the release until the next cycle.