Deployment of D9 2.31.0 is complete for production sites and is now commencing on non-production sites. The deployment block has now been lifted.
Posted May 23, 2023 - 16:02 AEST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted May 23, 2023 - 05:00 AEST
Scheduled
Advice - Who is affected: GovCMS Drupal 9 (D9) community. - Distribution will be updated on Monday 22 May 2023. - It addresses a recent security advisory issued by Drupal.org. - CKEditor5 module has been installed/added to the distribution. - No modules are being removed from the distribution. - No outages are expected to websites during the deployment process. - The D9 distribution will continue to be supported after this update. - If you have any concerns, raise a ticket at https://www.govcms.support
This update will install CKEditor5 in the distribution. For your project CKEditor4 will remain the default text editor. If you would like to continue familiarising yourself with CKEditor5, you will need to request for it to be enabled via a service desk ticket. This will enable you continue testing in a feature branch.
If you’re comfortable with CKEditor5 and would like one less thing to worry about in the D10 upgrade, you can enable CKEditor 5 as your default text editor from now.
Deployment schedule plan: - Commence from 5:00AM (AEST) Tuesday 23 May 2023 - Production branches completed by COB: 5:00PM (AEST) Tuesday 23 May 2023 - Once production branches are completed, status page will be updated and Non-Production branches will kick off - Non-Production branches should be completed by 10:00 AM (AEST) Thursday 25 May 2023
❗ IMPORTANT NOTICE 1: Deployments during maintenance window - During the scheduled maintenance window, ALL D9 SaaS deployments will be blocked while we deploy to the D9 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.
Information for PaaS customers - If you use the GovCMS D9 distribution, you should aim to apply this update to your distribution as soon as possible. - Updated files will be available from https://github.com/govCMS/GovCMS/releases/tag/2.31.0