Continuous Integration / config (pull_request) Successful in 51s
Continuous Integration / prepare (pull_request) Successful in 1m42s
Continuous Integration / build-production (pull_request) Skipped
Continuous Integration / test (pull_request) Successful in 2m1s
Continuous Integration / build (pull_request) Successful in 2m0s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 2m57s
Continuous Integration / deploy-production (pull_request) Skipped
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1.9 KiB
1.9 KiB
Joint release checklist (SLS, ASF, CMS)
Replaces the separate Deployment Setup, Monitoring Setup and Production Readiness stages of the features that are merged to master on 2026-11-16 (decision of the owner). Executed once, at the joint release moment. Every step needs the explicit go of the owner.
Status on 2026-11-16: everything is merged to master and runs on TEST only. No production release has been made.
Before the release moment
- ASF IIS publish pipeline exists (own feature: self-contained win-x64 publish, FTP upload, web.config, the CMS host as the single entry for the website; open hosting questions are answered by trying it with ASF).
- Hero module feature decided (release with or without it).
- Privacy statement and static texts reviewed by the owner (kept aside until now).
- Captcha provider decided (Gitea issue #14,
docs/captcha-providers.mdin the CMS repo). Captcha stays OFF in production until then.
Merge state (done 2026-11-16)
- Order: CMS (
contact-forms-module) first, then ASF (asf-packages-cms, test-only commit d449e76 removed), then SLS (redesign-modern-timetravel). - A push to master deploys to test only. Production is only started by a manual dispatch (ASF: only from a
release/branch). - CMS branch protection: required checks
backend-testandfrontend-testonly.
Release steps (production)
- SLP production environment:
Website__NoIndex=false,Website__PublicBaseUrl=https://slpsoftware.nl. - Contact retention configured (12 months for messages) and checked.
- Deploy CMS (
deploy_sls_production), then the SLS website (deploy_production), then ASF via the IIS pipeline. - IIS passes ALL requests to the CMS host for ASF.
- After release: check Sentry (errors, release tag), smoke tests per site, share image and sitemap, contact form end to end (one real message), cookies and statistics as described in the privacy statement.
- Update requirements and docs to the production state.