chore: update waku dependencies

[JulesFiliot]

• Closes part of this Update Waku dependencies #753
• Update waku dependencies
• Update to node 22 as required by new version of waku dependencies
• Upgrade all packages not compatible with node 22, especially those related to contentlayer (c.f. https://github.com/contentlayerdev/contentlayer?tab=readme-ov-file)

⚠️ Unfortunately Contentlayer is no longer maintained due to lack of funding. You can find a fork of the project here.

[changeset-bot]

🦋 Changeset detected

Latest commit: 859cc95

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@status-im/status-network	Minor
status.network	Minor
status.app	Minor
portfolio	Minor
api	Minor
hub	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
status-website	Ready	Preview	Comment	Nov 14, 2025 10:20am

5 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
status-api	Ignored	Preview		Nov 14, 2025 10:20am
status-components	Ignored	Preview		Nov 14, 2025 10:20am
status-network-hub	Ignored	Preview		Nov 14, 2025 10:20am
status-network-website	Ignored	Preview		Nov 14, 2025 10:20am
status-portfolio	Ignored	Preview		Nov 14, 2025 10:20am

[JulesFiliot]

I wanted to release the update as a major update since we move from node 20 to 22 and it's a breaking change but we didn't publish any major release yet so I'm leaving this as minor for now.

[felicio]

@JulesFiliot please, do you plan to upgrade the actual Waku dependencies and use of their APIs in this one (in packages/status-js)?

[JulesFiliot]

@JulesFiliot please, do you plan to upgrade the actual Waku dependencies and use of their APIs in this one (in packages/status-js)?

@felicio oh wow yes good catch thanks. I actually did all the work of updating to node 22 to be able to update the Waku dependencies in status-js but totally forgot to actually bump the Waku packages... I will handle it since it was the original goal.

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	0adb166	#6	2025-11-14 09:59:05	~50 sec	connector	📦zip
✔️	0adb166	#6	2025-11-14 09:59:42	~1 min	wallet	📦zip

[JulesFiliot]

@status-im/web everything is building with node 22 and the new dependencies of waku, all test passes on status-js package. I tested status-website and status-network-website but it's complex to know if everything else is working correctly with my current knowledge of the DB and projects. So if you could help me confirm everything is as it should be please, especially ex-status team 🙏