Releases · protocolbuffers/protobuf-javascript
v4.0.2-rc7
Using bzlmod with Bazel 7 or later:
Add to your MODULE.bazel file:
bazel_dep(name = "protobuf_javascript", version = "v4.0.2-rc7")
What's Changed
Full Changelog: v4.0.2-rc6...v4.0.2-rc7
v4.0.2-rc6
Using bzlmod with Bazel 7 or later:
Add to your MODULE.bazel file:
bazel_dep(name = "protobuf_javascript", version = "v4.0.2-rc6")
What's Changed
Full Changelog: v4.0.2-rc5...v4.0.2-rc6
v4.0.2-rc5
Using bzlmod with Bazel 7 or later:
Add to your MODULE.bazel file:
bazel_dep(name = "protobuf_javascript", version = "v4.0.2-rc5")
What's Changed
Full Changelog: v4.0.2-rc4...v4.0.2-rc5
v4.0.2-rc4
Bump version to 4.0.2-rc4 for testing BCR workflow
v4.0.2-rc3
Add placeholder google-protobuf.js file to fix missing input Release workflow currently errors out with `//:dist_files: missing input file '//:google-protobuf.js'` because we normally only generate it as part of the cross-compiled binary and npm releases. However, this seems to be causing problems for the BCR release process because the build target is broken without it. This change just adds a placeholder file to smooth things over.
Bump version to 4.0.2-rc2 for testing BCR workflow
v4.0.2-rc2 Bump version to v4.0.2-rc2 or testing BCR workflow
v4.0.2-rc1
Bump version to 4.0.2-rc1 for testing BCR workflow (#265) The BCR publishing workflow requires a tag, and we can't use v4.0.1 since it didn't yet contain the actions. We will hold off doing an actual plugin release to npm until BCR is settled.
v4.0.1
- Add support for protobuf edition 2024
- Add
--versionargument to protoc-gen-js binary for easier version checking. E.g. running./protoc-gen-jswill yield4.0.1.
v4.0.0
What's Changed
- Backport: binary proto serialization/deserialization changes and enable protobuf Editions 2023 (breaking change)
- Backport: Fix JSPB binary utf8 decoding and validate by default (breaking change)
- Do not ignore descriptor extensions
- Limit global resolution to globalThis by (breaking change)
v3.21.4
Release to fix bazel build layering issue in 3.21.3.