Conversation
63e9812 to
bd36ee8
Compare
bd36ee8 to
987f69a
Compare
|
Scope note: I intentionally kept the README commitment limited to the current CI surface: state the conformance target, run the official suite, and make the results visible. Broader roadmap language could be premature unless maintainers have time and support to own that work. For conformance specifically, useful follow-ups include enabling a binary threshold gate, validating newer upstream runners, and settling UTF-8 VERIFY behavior using TextEncoder/TextDecoder in a major release where stricter decoding can be treated as a breaking change. More broadly, protobuf.js would also benefit from native ESM and BigInt, a platform support bump (minimum Node v12.11.0 for |
Adds CI coverage for the official Protocol Buffers conformance suite and uploads the generated logs as artifacts.
The workflow currently runs against upstream v33, but the generator is prepared for v34.1/v35-rc1 where required EditionUnstable cases are present when testing up to Edition 2024. This requires a workaround on our end because the parser intentionally only accepts released editions.
Also updates the README.
Current results