NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1634 by repository stars
Last release 8 days ago
30 Sep 2026
Ships unpredictably
gaps range from 2 weeks to 3.1 years
Most releases are documented
notes for 6 of 9 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
70 releases · first in 2014
Use Go modules by @klauspost in #65
Full Changelog: v1.2.6...v1.2.7
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
AddingPowerSupport_CI/Testing by @santosh653 in #37
Full Changelog: v1.2.5...v1.2.6
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
reader: Fix missing buffers - #35
reader: Fix missing buffers - #35
Never return negative values from Write, as they can panic in `bufi…
Never return negative values from `Write`, as they can panic in `bufi…
…o` (#33)
* Never return negative values from `Write`, as they can panic in `bufio`
Nothing published for this version
pgzip: Fix an occasional segfault/panic with pgzip
pgzip: Fix an occasional segfault/panic with pgzip (#30)
This change fixes a occasional (5-10 out of 1000 test runs) segfault/panic on
sync.Pool struct access. Basically what happens there is that the original code
assigns a zero-value sync.Pool struct to the existing z.dstPool variable.
In general this kind of assignment is safe only if object is not used anymore /
in parallel by anything else. While is kind of true in a sense that none of the
goroutines are using it, in case of sync.Pool the garbage collector does
special management of the data with weak references and in right weather
conditions corrupts internal state (more precisely the sync.Pool.local might
become nil before reading it but after reading a nonzero sync.Pool.localSize;
leading to invalid memory reference in sync.Pool.Get() ).
godoc: added new Default values for SetConcurrency
godoc: added new Default values for SetConcurrency (#29)
it seems that the default was changed and the function documentation was wrong
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →