Deployments of D11 4.5.1.1 hotfix are complete for production sites and are now commencing on D11 non-prod sites. The deployment block has been lifted.
Posted Sep 30, 2026 - 12:19 AEST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Sep 30, 2026 - 06:00 AEST
Scheduled
Advice We would like to inform you of the upcoming GovCMS Drupal 11 (D11) hotfix release and deployment. It addresses recent security advisories issued by Drupal.org. GovCMS assessed the CRITICAL risk as they applied to D11 distribution, subsequently the security residual risk remained CRITICAL. The D11 distribution will continue to be supported after this update.
Deployment schedule: - Deployment to commence from 6am Wednesday 30 September 2026 and will be conducted throughout the daytime. - Production branches completed by 3pm Wednesday 30 September 2026 - Non-Production branches completed by 10am Thursday 1 October 2026
As a reminder, a SaaS deployment block is in place ONLY while we update the production branches. During this time, you will still be able to develop and deploy to non-production feature branches. PaaS deployments schedules are not impacted.
SaaS Actions:
All D11 SaaS customers will need to check their website after the deployment to ensure there aren’t any issues.
IMPORTANT NOTICE 1: deployments during maintenance window
During the scheduled maintenance window, ALL D11 SaaS deployments will be blocked while we deploy to the D11 master/production environments. While the production block is on, you will still be able to develop and deploy to non-production feature branches.
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. Not rebasing your codebase could result in your new database configuration reverting to an older version when you next deploy, potentially causing issues for your website.
All subsequent commits will be blocked in the CI pipeline until this merge request branch is deleted.
If no merge request is lodged after a release, then no configuration has changed and no further action is required.
Drupal Core 11.4.x Preview GovCMS is midway through the preview periodfor the next Drupal Core update from 11.3.x to 11.4.x and PHP update from 8.3 to 8.5. The preview feature branch will be available for available 16 September – 7 October
Configuration Management Prior to the next scheduled release and update 4.6.0, GovCMS will be implementing a scheduled monthly stale configuration cleanup exercise. For more information see Knowledge Base article: https://govcms.freshdesk.com/support/solutions/articles/51000490006