This sprint we were mostly focused on the stable release of Silverstripe CMS 4.11.0 and the ongoing work to migrate our CI pipeline from travis-ci to Github actions. We’ve also reviewed a few of our processes which culminated in updated github labels and definitions to make it easier for us to prioritise high-value issues.
Release sprints are pretty hectic - the lists below may not be impressive but don’t let that fool you.
- Silverstripe CMS 4.11.0 was released
- a PHP8.1 compatibility issue with MySQL PDO is fixed in silverstripe/framework 4.10.10 and 4.11.2
The CMS Squad isn’t working alone - there are a bunch of amazing developers in the wider community helping to improve Silverstripe CMS. A big thank you to everyone who creates a PR, raises an issue, offers feedback, etc. Here are some of the community PRs that were merged in supported modules this sprint.
- typecast vars to ensure the value is an array from Jordy Rosenbrand
- Allow for optional can permission method for content review from Mo Alsharaf
- [v4] Relax possible filter value types from Roman Schmid
- fix: Syntax for declaring enums in YML from Roman Schmid
- FIX: ‘passwordsent’ title was not being displayed from Loz Calver
- ENH fix missing styling on success message from Will Rossiter
- FIX: Add missing casting for Form::getAttributesHTML from Loz Calver
- Handle null values passed to PDO::quote() from Brandon Iffert
- fix: public health/check should not include full details from Will Rossiter
- Work continues on migrating our CI pipeline to Github actions
- This also includes tightening our standards somewhat and improving infrastructure test coverage
- Preparing for CMS5 development
- Various bug fixes and quality-of-life improvements