Gofrs Uuid Versions Save

This release adds a new constant for the Max UUID. Max UUID defined in draft-ietf-uuidrev-rfc4122bis-14 as having maximum values for all bits.

NOTE: Because this feature is part of a draft, it is subject to removal on a minor version of this package if it is removed from a later revision of the RFC.

• Added Max UUID, contributed by @james-lawrence

Full Changelog: v5.1.0...v5.0.1

• Fixed an issue with TimestampFromV7 reporting the wrong UUID version in the error message, contributed by @jaredLunde and @PatrLind

Full Changelog: v5.0.1...v5.0.0

This is a major release that changes no behavior of the package since the previous release (v4.4.0) and only incorporates gomodules.

• Made this package compatible with gomodules #116 , contributed by @cameracker

Full Changelog: v4.4.0...v5.0.0

• Improved performance and reduce memory allocations for most UUID methods, contributed by @charlievieth (#96)
• Added a generator constructor that accepts options, contributed by @mlesar, completed by @LeonanCarvalho (#111)
• UUID now satisfies driver.Valuer and sql.Scanner interfaces, contributed by @charlievieth (#113)
• Update UUIDv7 to conform with RFC Draft Rev 4, contributed by @bgadrian (#112)

NOTE: This release uses Time.UnixMilli() internally which is only available on Go 1.17 or later.

Full Changelog: v4.3.1...v4.4.0

• Update UUIDv7 to use unix millisecond calculation that is friendly to legacy go versions by @convto Full Changelog: v4.3.0...v4.3.1

• Update UUIDv7 to conform with RFC Draft Rev 3 by @convto (Breaking change to experimental feature)
• Update unit test coverage to be 100% by @theckman, and @cameracker

Full Changelog: v4.2.0...v4.3.0

Changes

Addition of IsNil method by @jordan-chalupka in #95

Full Changelog: v4.10...v4.2.0

Changes

• initial implementation of UUIDv6 and UUIDv7 based on RFC Draft Rev 2 by @theckman in https://github.com/gofrs/uuid/pull/93

Full Changelog: https://github.com/gofrs/uuid/compare/v4.0.0...v4.1.0

• This release removes support for UUIDV2. UUID V2 is underspecified and unsafe for users expecting uniqueness - the time dependence frequently produces duplicate identifiers and V2 is dependent on *nix only time features. UUID V2 is especially weak on Windows operating systems.

We recommend that all users of the library either upgrade to this version, or at least consider no longer relying on UUID V2 in their applications.

Note: This release is identical to v3.3.0 and was created by mistake. It is safe to use either.

• the UUID type now satisfied fmt.Formatter; see the .Format() method docs for more info. Contributed by Dylan Bourque (@dylan-bourque) in #72.
• Codec related error messages have been adjusted to improve clarity and consistency with error message standards. Contributed by Josh Leverette (@coder543 ) in #78.