NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1731 by repository stars
Latest stable
v1.5.1
Last release 7 years ago
no release in 18 months
Release timing varies
gaps range from 8 days to 3 months
Nearly every release is documented
notes for 19 of 20 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
25 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
This release is outdated. Upgrading to v2.0.1 or newer is recommended.
This release is outdated. Upgrading to v2.0.1 or newer is recommended.
Changes include:
Fuzzing passed 500+ million execs on Feb 9, 2020.
This release adds encoding options while maintaining backward compatibility.
This release adds encoding options while maintaining backward compatibility.
With EncOptions.ShortestFloat = ShortestFloat16, floating-point values (including subnormals) encode
float64 -> float32 -> float16 when values can round-trip. This is optimized by avoiding the round-trip test except for a subset of subnormal input values and using a faster test for other values.
Conversions for infinity and NaN use InfConvert and NaNConvert settings.
New functions like CanonicalEncOptions(), CTAP2EncOptions(), etc. return predefined EncOptions that can be modified to create custom configurations.
Changes include:
UPDATE: Fuzzing passed 4.75+ billion execs with Go 1.12 on Jan. 22, 2020.
Fuzzing passed 2.88+ billion execs with Go 1.13 on Jan. 31, 2020 (slower machine).
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Feature: Deprecate bool encoding options and add int SortMode (commit 3b78ee0)
Release v1.4.0 (Dec 25, 2019)
Changes include:
Fuzzing passed 532+ million execs with Go 1.12 at the time of release.
Fuzzing passed 4+ billion execs with Go 1.13 about 17-18 days after release.
v1.3.1 to v.1.3.4 benefited from extensive code review and refactoring.
Release v1.3.4 (Dec 18, 2019)
v1.3.1 to v.1.3.4 benefited from extensive code review and refactoring.
Changes include:
Fuzzing reached 370+ million execs with Go 1.12 at the time of release.
Update: On Dec. 25, 2019, fuzzing passed 2+ billion execs with Go 1.13.
corpus: 1092 (46h8m ago), crashers: 0, restarts: 1/10000, execs: 2028736632 (3194/sec), cover: 2006, uptime: 176h27m
Fix: Fix panic when encoding new type with float32 as its underlying type (commit bb1c06a)
Release v1.3.3 (Dec 9, 2019)
Changes include:
Fuzzing reached 276+ million execs at the time of release.
UPDATE: It continued fuzzing and reached 2.79+ billion execs about 8 days after release.
workers: 2, corpus: 1074 (44h26m ago), crashers: 0, restarts: 1/10000, execs: 2796329664 (3386/sec), cover: 2011, uptime: 229h25m
This release checks for additional issues while decoding well-formed CBOR messages.
Release v1.3.2 (Nov 27, 2019)
This release checks for additional issues while decoding well-formed CBOR messages.
Changes include:
A separate project, cbor-fuzz was updated to use new fxamacker/cbor features it had missed. Cover is noticably higher (better) during fuzzing.
UPDATE: Fuzzing reached 4.2+ billion execs on Dec 3, 2019. Corpus is temporarily low (as shown here) for v1.3.2, but it's already 1000+ after combining Go 1.12 + Go 1.13 fuzzing corpus folders after this run.
2019/12/03 15:37:19 workers: 2, corpus: 602 (12h17m ago), crashers: 0, restarts: 1/10000, execs: 4226276531 (7203/sec), cover: 2000, uptime: 162h59m
Issue #46 resulted in filing an errata to RFC 7049 (CBOR) after the same mistake was found in both 7049 and Wikipedia. RFC 7049 author (cabo) confirme
Release v1.3.1 (Nov 24, 2019)
Issue #46 resulted in filing an errata to RFC 7049 (CBOR) after the same mistake was found in both 7049 and Wikipedia. RFC 7049 author (cabo) confirmed within an hour directly in #46 which was super nice of him.
I'll let fuzzing continue for 1-10 days, due in part to issue #46 and initial valid fuzzing corpus. Maybe it'll generate fewer corpus files this time to reach a good stopping point.
Most users of v1.3.0 won't notice any practical difference from these bugfixes. They involve data validation rules and an obscure difference in sorting rule for canonical encoding.
Changes include:
This release passed 877k+ executions (19 hours, and still running) of coverage-guided fuzzing using fxamacker/cbor-fuzz.
workers: 2, corpus: 403 (48s ago), crashers: 0, restarts: 1/10000, execs: 877930249 (12405/sec), cover: 1501, uptime: 19h39m
Nothing published for this version
New struct tags "keyasint" and "toarray" make it easy to use Go structs with CBOR maps and arrays. Using COSE, CWT, SenML, etc. is more natural with l
New struct tags "keyasint" and "toarray" make it easy to use Go structs with CBOR maps and arrays. Using COSE, CWT, SenML, etc. is more natural with less programming effort.
Encoding and decoding speed is faster than prior releases due to safe optimizations. Encoding speed and structs got the biggest speedups.
Benchmark comparisons are hard in v1.3 because older releases lack "keyasint" and "toarray". Some of the biggest speedups are from no longer having to use Go maps with COSE, CWT, SenML, etc.
Specific changes include:
This release passed 2+ billion executions (72 hours) of coverage-guided fuzzing using fxamacker/cbor-fuzz v0.7.0:
workers: 2, corpus: 719 (72h27m ago), crashers: 0, restarts: 1/10000, execs: 2275843330 (8725/sec), cover: 1492, uptime: 72h27m
Nothing published for this version
Feature: Add RawMessage, Marshaler, and Unmarshaler (commit 1a2918702e980f0776663d11290dfe40e20a8c08)
Changes include:
This release passed 42 hours of fuzzing with fxamacker/cbor-fuzz v0.7.0.
Nothing published for this version
Prevent an inappropriate use of BinaryUnmarshaler.
Prevent an inappropriate use of BinaryUnmarshaler.
Specifically, don't allow CBOR byte string (major type 2) as input to Go's Time.UnmarshalBinary.
Time values should only be encoded/decoded using these CBOR data types: pos or neg integer, float, and text string. For more info, see RFC 7049 section 2.4.1.
For details, see commit 34ffc3a3fd37df109c2ea1887de5ec8848a11fd8.
This release passed 24+ hours of fuzzing with fxamacker/cbor-fuzz v0.6.0.
Improve slice encoding speed by 50%, struct by 30%, and map by 14%.
Improve slice encoding speed by 50%, struct by 30%, and map by 14%.
For details, see commit 29e05d7.
Add support for encoding.BinaryMarshaler and encoding.BinaryUnmarshaler interfaces.
Add support for encoding.BinaryMarshaler and encoding.BinaryUnmarshaler interfaces.
For details, see commit 602ddc7 closing Issue #5.
Code refactoring and README updates.
Nothing published for this version
cbor v1.0.0 stable for Go 1.12+.
cbor v1.0.0 stable for Go 1.12+.
Refactored and improved test coverage to 97%:
Refactored and improved test coverage to 97%:
Nothing published for this version
Add feature to handle JSON struct field tags, see details.
Add feature to handle JSON struct field tags, see details.
Add encoding and decoding support for time.Time.
Add encoding and decoding support for time.Time.
Add encoding support for indefinite length bytes/string/array/map, with updated tests, examples, and README.
Add encoding support for indefinite length bytes/string/array/map, with updated tests, examples, and README.
cbor will only support Go 1.12 and newer. This allows cbor to use new API in reflect package for performance gain.
cbor will only support Go 1.12 and newer. This allows cbor to use new API in reflect package for performance gain.
This release includes bug fixes, performance improvements, and documentation updates, detailed below.
Changelog:
Nothing published for this version
One column per quarter.