From 5ad1847c42d835ab01b2e117e5d77497a6264dd9 Mon Sep 17 00:00:00 2001
From: "blink-so[bot]" <211532188+blink-so[bot]@users.noreply.github.com>
Date: Thu, 3 Jul 2025 19:45:12 +0000
Subject: [PATCH] fix: add manual confirmation for release calendar update
 (#18748)

Add a confirmation dialog to the release script that prompts the user to
manually update the release calendar documentation before proceeding
with the release.

## Changes

- Added a confirmation prompt that asks users to update the release
calendar documentation
- Provides the URL to the documentation
(https://coder.com/docs/install/releases#release-schedule)
- Suggests running the `./scripts/update-release-calendar.sh` script
- Requires explicit confirmation before proceeding with the release
- Exits the script if the user hasn't updated the documentation

## Testing

- [x] Script syntax validation passes (`bash -n scripts/release.sh`)
- [x] Changes are placed at the appropriate point in the release flow
(after release notes editing, before actual release creation)

This addresses the issue where the release calendar documentation was
getting out of date. While automation can be added later, this ensures
users manually confirm the documentation is updated before each release.

Co-authored-by: blink-so[bot] <211532188+blink-so[bot]@users.noreply.github.com>
Co-authored-by: bpmct <22407953+bpmct@users.noreply.github.com>
---
 scripts/release.sh | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/scripts/release.sh b/scripts/release.sh
index 6f11705c30..8282863a62 100755
--- a/scripts/release.sh
+++ b/scripts/release.sh
@@ -308,6 +308,21 @@ if [[ ${preview} =~ ^[Yy]$ ]]; then
 fi
 log
 
+# Prompt user to manually update the release calendar documentation
+log "IMPORTANT: Please manually update the release calendar documentation before proceeding."
+log "The release calendar is located at: https://coder.com/docs/install/releases#release-schedule"
+log "You can also run the update script: ./scripts/update-release-calendar.sh"
+log
+while [[ ! ${calendar_updated:-} =~ ^[YyNn]$ ]]; do
+	read -p "Have you updated the release calendar documentation? (y/n) " -n 1 -r calendar_updated
+	log
+done
+if ! [[ ${calendar_updated} =~ ^[Yy]$ ]]; then
+	log "Please update the release calendar documentation before proceeding with the release."
+	exit 0
+fi
+log
+
 while [[ ! ${create:-} =~ ^[YyNn]$ ]]; do
 	read -p "Create, build and publish release? (y/n) " -n 1 -r create
 	log