Update - Deployment of D10 3.29.0 is complete for production sites and is now commencing on non-production sites. The deployment block has now been lifted.
Feb 24, 2026 - 21:16 AEDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 24, 2026 - 06:00 AEDT
Scheduled - Advice - Who is affected: GovCMS Drupal 10 (D10) community. - No outages are expected to websites during the deployment process. - The D10 distribution will continue to be supported after this update. - If you have any concerns, raise a ticket at https://www.govcms.support
Schedule: - Distribution was released on Tuesday 17 February 2026 - Deployments to commence from 6am Tuesday 24 February 2026 and will be conducted throughout the day - Production branches completed by 10am (AEDT) Wednesday 25 February 2026 - Once production environments are completed, status page will be updated and Non-Production environments will kick off - Non-Production branches completed by 10am (AEDT) Thursday 26 February 2026
❗ 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 environments. - 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.
Distribution Updates:
- Stage File Proxy settings
What modules are added/marked obsolete/uninstalled/removed in the distribution?
The following modules have been marked as obsolete:
- End of Life Core modules - End of Life Webform sub-modules - Panelizer Quick Edit and Panels IPE modules
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 - updated files will be released on 17 February 2026 - available from https://github.com/govCMS/GovCMS/releases/tag/3.29.0 - you should aim to apply this update to your distribution as soon as possible.
GovCMS: Content management and website hosting for the Australian government. Managed by the Department of Finance with service delivery partners Salsa Digital and amazee.io
Completed -
Due to unforeseen technical issues, this deployment is not going ahead today. We will advise when the rescheduled date is known.
Feb 18, 08:47 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 18, 06:00 AEDT
Scheduled -
Advice - Who is affected: GovCMS Drupal 10 (D10) community. - No outages are expected to websites during the deployment process. - The D10 distribution will continue to be supported after this update. - If you have any concerns, raise a ticket at https://www.govcms.support
Schedule: - Distribution was released on Tuesday 17 February 2026 - Deployments to commence from 6am Wednesday 18 February 2026 and will be conducted throughout the day - Production branches completed by 10am (AEDT) Thursday 19 February 2026 - Once production environments are completed, status page will be updated and Non-Production environments will kick off - Non-Production branches completed by 10am (AEDT) Friday 20 February 2026
❗ 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 environments. - 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.
Distribution Updates:
- Stage File Proxy settings
What modules are added/marked obsolete/uninstalled/removed in the distribution?
The following modules have been marked as obsolete:
- End of Life Core modules - End of Life Webform sub-modules - Panelizer Quick Edit and Panels IPE modules
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 - updated files will be released on 17 February 2026 - available from https://github.com/govCMS/GovCMS/releases/tag/3.29.0 - you should aim to apply this update to your distribution as soon as possible.
Resolved -
Between 10 February 2026 and 16 February 2026, password reset emails from Gitlab failed to send. This is now resolved - the password reset process should work as expected. We apologise for any inconvenience.
Feb 16, 16:14 AEDT
Completed -
The scheduled maintenance has been completed.
Feb 16, 09:07 AEDT
Update -
Deployment of D10 3.28.3 is complete for production sites and is now commencing on non-production sites. The deployment block has now been lifted.
Feb 11, 17:39 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 11, 06:00 AEDT
Scheduled -
Advice - Who is affected: GovCMS Drupal 10 (D10) community. - No outages are expected to websites during the deployment process. - The D10 distribution will continue to be supported after this update. - If you have any concerns, raise a ticket at https://www.govcms.support
Schedule: - Distribution was released on Tuesday 10 February 2026 - Deployments to commence from 6am Wednesday 11 February 2026 and will be conducted throughout the day - Production branches completed by 10am (AEDT) Thursday 12 February 2026 - Once production environments are completed, status page will be updated and Non-Production environments will kick off - Non-Production branches completed by 10am (AEDT) Friday 13 February 2026
❗ 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 environments. - 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.
What modules are added/marked obsolete/uninstalled/removed in the distribution?
- Services TFA submodule
Information for PaaS customers
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 - updated files will be released on 10 February 2026 - available from https://github.com/govCMS/GovCMS/releases/tag/3.28.3 - you should aim to apply this update to your distribution as soon as possible.