Skip to content

Releases: gofrs/uuid

2.0.0

18 Jul 19:53
@theckman theckman
v2.0.0
This tag was signed with the committer’s verified signature. The key has expired.
theckman Tim Heckman
GPG key ID: C49EB0B238492FC1
Expired
Learn about vigilant mode.
09c29bc
This commit was signed with the committer’s verified signature. The key has expired.
theckman Tim Heckman
GPG key ID: C49EB0B238492FC1
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.0.0

This is first release of this package as github.com/gofrs/uuid, after having
been forked from github.com/satori/go.uuid at 36e9d2e.

The reason behind the decision to fork was due to lack of engagement from the
original author, when there were fatal bugs present. The intent is to keep up
the support of this package by not having the burden rest on one individual.

This is a major version bump as the forked project introduced breaking
changes (0ef6afb) after v1.2.0 that were never captured in a release. These
changes were the addition of error return values of some of the UUID generation
methods.

A major bug was fixed (#7) that would have resulted in UUIDs that weren't so
unique. The original bug report is here: satori/go.uuid#73

In addition to that, some small API enhancements/fixes were made:

  • export the default generator used by the package-level functions as
    DefaultGenerator (#9)
  • update code to work as documented by supporting braced hashlike UUIDs in the
    FromString callpath (#14)
  • remove named return values from the function definitions (#25)
  • linter caught an issue where an error value was shadowed (#10)

While they have no impact on the functional usage of this package, the following
improvements were also made in areas ranging from docs to testing:

  • set up Travis CI for testing and coveralls for coverage (#6)
  • we stopped testing against older versions of Go, to support subtests (#21)
  • tests no longer use gocheck and are stdlib only (#17)
  • added support for fuzz testing (#5 #17)
  • enhanced tests to improve coverage (catch issues) (#3 #24)
  • fixed linter issues around variable names (#10)
  • updated docs to be more clear and correct (#8 #12 #16 #28 #29)
  • recommend that consumers only use 2.0.0+ at this point (#30)

This release wouldn't be anywhere near as polished if it weren't for the help of
a few people in the Go community. Alphabetized by their GitHub handles:

There are also a few people who provided input in the #gofrs Slack channel or on
issues / PRs:

  • Cameron Ackerman (@CameronAckermanSEL)
  • Timur Makarchuk (@makarchuk)
Assets 2
Loading