Deployment of D10 3.17.1 is complete for production sites and is now commencing on non-production sites. The deployment block has now been lifted.
Posted Oct 10, 2024 - 14:07 AEDT
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Oct 09, 2024 - 06:00 AEDT
Scheduled
Advice GovCMS will release the Drupal 10 (D10) distribution on Tuesday 8 October 2024. Deployment is scheduled to commence from 6:00am Wednesday 9 October 2024 and will be conducted throughout the day. No outages are expected to websites during the deployment process.
It addresses a recent security advisory issued by Drupal.org. GovCMS assessed the critical risk as they applied to D10 distribution, subsequently the security residual risk remained critical. The D10 distribution will continue to be supported after this update
Deployment schedule plan: - Production branches completed by 10:00am (AEST) Thursday 10 October 2024. - Non-Production branches completed by 10:00am (AEST) Friday 11 October 2024. - PaaS deployments schedules are not impacted.
PaaS Actions Update your codebase to ensure you are running the latest platform base images and packages and stay aligned to GovCMS best practice:
GovCMS D10 distribution: - includes module updates addressing Drupal security vulnerabilities. - updated files will be released on Tuesday 8 October 2024 - available from GitHub release tag 3.17.1 (https://github.com/govCMS/GovCMS/releases/tag/3.17.1)
SaaS Actions ❗ IMPORTANT NOTICE 1: Deployments during maintenance window - During the scheduled maintenance window, ALL D10 SaaS deployments will be blocked while we deploy to the D10 Production branches. - While the production block is on, you will still be able to develop and deploy to non-production feature branches. - PaaS deployments schedules are not impacted.
❗ IMPORTANT NOTICE 2: Update local environments - Ensure you update your local environments to the latest release. Not rebasing your codebase results in mismatched database configuration causing errors in forklifts and deployments.
❗ IMPORTANT NOTICE 3: For customers with configuration management enabled - The latest configuration from your production database has been created for you in GitLab in a branch called action-required/latest-config-export. - You need to review and test the changes in the merge request. Once you are satisfied, please check the “Delete source branch” box and click “Merge”. - This MUST be done before any new commits. - All subsequent deployments will be blocked in the CI pipeline until this merge request branch is deleted - Not merging the latest configuration provided could result in your new database configuration reverting to an older version when you next deploy, potentially causing issues for your website. - If no merge request is lodged after a release then no configuration has changed and no further action is required.
Posted Oct 04, 2024 - 12:26 AEST
This scheduled maintenance affected: GovCMS Projects (Individual websites).