Vortex 1.35, released as Radiance, is a keeping-current release. Drupal 11.3 landed upstream and the template moved with it. Alongside that, coverage reporting became visible where you actually make decisions, and one everyday command changed shape. There are no breaking changes in this one.
Drupal 11.3 support, on arrival
The gap between a Drupal core release and the point where your project can safely take it is where most upgrade debt starts. A minor version lands, your team is busy, and 6 months later you are 2 versions behind and the jump has stopped being routine.
This release adds compatibility for Drupal 11.3.0, so a project built on Vortex can take the update as part of normal dependency maintenance. There is nothing to configure. It is the kind of change you only notice when it is missing.
Test coverage shows up on the pull request
Coverage numbers have a habit of living somewhere nobody looks. They are generated in CI, written to a log, and read by whoever remembers to go looking after a build finishes.
Vortex now posts the coverage result as a comment on the pull request itself. The number arrives next to the diff it belongs to, while the decision to merge is still open. Reviewers get the signal without leaving the page, and a drop in coverage becomes something the team talks about during review.
ahoy test now runs PHPUnit only
This one is worth knowing about, because the command still exists and its behaviour changed.
ahoy test used to run PHPUnit and Behat together. It now runs the PHPUnit suites only. Behat tests run through ahoy test-bdd, which has always been there.
The reason is speed at the point of use. A unit and kernel suite finishes in seconds, and browser tests take minutes. Keeping them behind separate commands means the quick check stays quick and you choose when to pay for the slow one. If you have a script or a CI step calling ahoy test and expecting both, point it at both commands.
PHPUnit test discovery in submodules was fixed in the same release, so tests living inside a custom submodule are found and run.
The demo theme drops Grunt
The demo theme shipped with Vortex used Grunt to build its front end. Grunt has been quiet for years, and a new project inheriting it inherits a toolchain nobody on the team has touched recently.
The demo theme now builds through NPM scripts. Fewer moving parts, a toolchain your front-end developers already use, and one less thing to explain to somebody joining the project.
Notifications that stay quiet until they are configured
Vortex sends deployment notifications to Slack, GitHub, email and New Relic. 2 fixes here are small enough to overlook and will save somebody an afternoon.
- New Relic notifications are skipped in environments where New Relic has not been set up, controlled by
VORTEX_NOTIFY_NEWRELIC_ENABLED. A half-configured environment stops producing failures that mean nothing. - Slack pre-deployment notifications send the correct environment URL and login link. The message used to arrive with a link that did not take you where you expected.
Upgrading
There are no breaking changes, so this is a routine update. The container images, GitHub Actions and Rector rules all move with it, and the Rector configuration stopped applying a rule that was rewriting form callbacks incorrectly.
The one behaviour change to check is ahoy test. If anything in your project relied on it running Behat as well, add ahoy test-bdd alongside it.
Full details are in the GitHub release notes(Opens in a new tab/window), and the Vortex documentation(Opens in a new tab/window) covers the commands above.
