We’re aiming to publish Meteor 3.3.4, 3.4.3, 3.5.4 and 3.6-rc.1 early this week, once the remaining verification is complete.
The security work in Meteor itself started well before the latest Node.js updates, based on internal reviews and reports shared privately with us. Those fixes were already included in the upcoming patches, and we’ve since added the Node.js security updates to the same releases.
The backports have needed some extra care around version compatibility. Each release line has different implementations and dependency constraints. We need to ensure the patched packages work together, that partial updates cannot introduce incompatible combinations, and that older backports don’t replace newer functionality in the 3.6 RC. We’ve been validating package resolution and running regression and example-app tests, with CI, build and publication checks.
Security is especially important today with AI, and we need to be prepared to deliver backported fixes quickly through a reliable, repeatable process. We’re committed to improving both the speed of our response and the validation behind each release.
That’s the motivation behind the release cadence and security backport strategy we’ve been discussing with the community. We’re putting considerable effort into turning what we learn into automated checks and reusable internal release workflows, so future security releases take less manual work and reach you sooner.
For this round, we’re keeping coverage from 3.3.x onwards. Going forward, we need a more manageable process and a realistic scope for how many older release lines we can maintain reliably. This work is helping us understand that cost and refine the approach.
We’ll announce the patches as soon as they’re available. I hope them for today or tomorrow depending on how the process goes. Thanks for your patience, and please keep supporting Meteor through testing, contributions and sponsorship. That support helps sustain this maintenance so we can all continue benefiting from it.