[feugy]

🖖 What's in there?

Bumps micro on 9.x to 9.3.5-canary.4. This canary ships #496: malformed Content-Type headers now return 400 instead of 500, for services that still use micro@9.3.5-canary.3.

🤺 How to test?

After merge, an npm owner of micro publishes:

git checkout 9.x && git pull
git tag v9.3.5-canary.4 && git push origin v9.3.5-canary.4
cd packages/micro && npm publish --tag canary

⚠️ --tag canary is required. Without it, npm moves latest from 10.x to this 9.x canary.

Then:

npm view micro dist-tags   # canary: 9.3.5-canary.4, latest: 10.x

🔬 Notes to reviewers

• Same shape as the v9.3.5-canary.3 release commit: lerna.json and packages/micro/package.json change.
• No build step: 9.x is plain JavaScript.
• Do not use the publish-canary script: its lerna config only allows the master and canary branches, and it pushes straight to the branch.

🔗 Related PRs

• fix: return 400 for malformed Content-Type header (9.x) #496: the fix.
• 10.0.2 #498: same release for main (10.0.2).

[jsvana]

9.x canary bump for the malformed Content-Type 400 fix.