workerd
1.20261120.1 · 20 Nov 2026Apache-2.053.4M / weekRepositoryHomepagenpmAtom feed
Upgrading workerd From 1.20230307.0 to 1.20230321.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 5
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.20230321.0
Security
1 advisory still affects 1.20230321.0
- Buffer under-read in workerdmoderate · GHSA-8vx6-69vg-c46f
Upgrading to 1.20230419.0 clears it.
Release by release
- Breaking
Breaking out trace and thread-scopes
- New
Implements TLS support for TCP sockets (with default TLS settings).
- New
Support bundling raw JavaScript in built-in bundles
- New
Add disk usage info to test plan
- New
Add initial port of Node.js Compat Streams
- New
Add more Node.js compat streams tests
- Breaking
13 other lines we could not sort, mostly version bumps
- 1.20230321.0
Disallow importing public ECDH keys with non-empty usage
- 1.20230321.0
Remove unused
Bodytype parameter fromEmailMessage - 1.20230321.0
Boringssl update
- 1.20230321.0
Move RequestTracker into workerd and use it in Worker::Actor
- 1.20230321.0
Switch to api.ast.json.gz instead of api.ast.json
- 1.20230321.0
Polyfill internal process.nextTick for Node.js compat
- 1.20230321.0
Use bazel6
- 1.20230321.0
bazel: Reuse sandbox directories
- 1.20230321.0
Split build and test steps in test action
- 1.20230321.0
Update to V8 11.0.226.19
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.