Skip to content

Commit 5ad1847

Browse files
blink-so[bot]bpmct
andauthored
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>
1 parent a099a8a commit 5ad1847

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

scripts/release.sh

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -308,6 +308,21 @@ if [[ ${preview} =~ ^[Yy]$ ]]; then
308308
fi
309309
log
310310

311+
# Prompt user to manually update the release calendar documentation
312+
log "IMPORTANT: Please manually update the release calendar documentation before proceeding."
313+
log "The release calendar is located at: https://coder.com/docs/install/releases#release-schedule"
314+
log "You can also run the update script: ./scripts/update-release-calendar.sh"
315+
log
316+
while [[ ! ${calendar_updated:-} =~ ^[YyNn]$ ]]; do
317+
read -p "Have you updated the release calendar documentation? (y/n) " -n 1 -r calendar_updated
318+
log
319+
done
320+
if ! [[ ${calendar_updated} =~ ^[Yy]$ ]]; then
321+
log "Please update the release calendar documentation before proceeding with the release."
322+
exit 0
323+
fi
324+
log
325+
311326
while [[ ! ${create:-} =~ ^[YyNn]$ ]]; do
312327
read -p "Create, build and publish release? (y/n) " -n 1 -r create
313328
log

0 commit comments

Comments
 (0)