Releases: protocolbuffers/protobuf-javascript
Releases · protocolbuffers/protobuf-javascript
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
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
v3.21.3
v3.21.2
v3.21.1
- Enable Closure's advanced optimization mode by default. This should reduce code size (#124).
- Replace goog.testing.asserts in tests with Jasmine expectations (#136).
- Bring in the subset of the goog.asserts we use as jspb.asserts. This code retains an Apache 2.0 license.
- Fix decoding of signed varint32s (#31).
- Add license files to NPM package.
This will also be our first release to have cross-compiled protoc-gen-js binaries. Please note that they use dynamic linking (similar to the protobuf protoc releases).