In this patch we addressed a security issue 
Tasks and fixes in this release:
Pull Requests for 3.2.2
Special thanks to the community contributors who made this release possible: [List of contributors]
@ShiyuBanzhou
@italojs
How to try it?
Installing Meteor
npx meteor
Existing projects:
meteor update --release 3.2.2
Starting a project:
meteor create app-name --release 3.2.2
Your help testing this version by creating a new app or migrating your current one will be extremely helpful!
Please give us your feedback, and if you find any issues, you can create a post here or open an issue on GitHub.
7 Likes
When will you release Meteor@3.3-beta.1?
1 Like
we plan on doing it soon-ish;
We have a two pending items, this PR and some docs changes but then I think we are ready to publish a new version.
5 Likes
After updrading , I started getting this message in local dev terminal
W20250510-12:21:37.333(5.5)? (STDERR) Sat, 10 May 2025 06:51:37 GMT router deprecated handlers that are Promise-like are deprecated, use a native Promise instead at …/…/…/…/…/…/…/…/.meteor/packages/webapp/.2.0.6.1j4r2bpbvox++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/router/index.js:342:13
I am using “react-router-dom”: “^6.30.0”, This may be the reason.
This happened after upgrading Express to 5.1.0. I thought it was added in 3.3 only, but it was merged in devel and landed in 3.2.2 apparently.
I wrote about it in the 3.3 changelog as a deprecation. Now apps need to identify which Express endpoints should use async/await with native promises, meteor/v3-docs/docs/generators/changelog/versions/3.3.0.md at release-3.3 · meteor/meteor · GitHub
This seems to be just a deprecation but not a breaking change yet.
- express@5.1.0 - Depends on Meteor’s webapp package.
- Deprecates non-native promise usage #154
- Use async/await or Promise.resolve when defining endpoints to avoid deprecation warnings.
1 Like
I will wait for 3.3 release.
