Skip to content

Releases: google/uuid

v1.6.0

Choose a tag to compare

@release-please release-please released this 23 Jan 18:54
0f11ee6

1.6.0 (2024-01-16)

Features

Bug Fixes

v1.5.0

Choose a tag to compare

@release-please release-please released this 12 Dec 17:21
4d47f8e

1.5.0 (2023-12-12)

Features

  • Validate UUID without creating new UUID (#141) (9ee7366)

v1.4.0

Choose a tag to compare

@release-please release-please released this 26 Oct 15:24
8de8764

1.4.0 (2023-10-26)

Features

  • UUIDs slice type with Strings() convenience method (#133) (cd5fbbd)

Fixes

  • Clarify that Parse's job is to parse but not necessarily validate strings. (Documents current behavior)

v1.3.1

Choose a tag to compare

@release-please release-please released this 21 Aug 16:29
b3cae7c

1.3.1 (2023-08-18)

Bug Fixes

  • Use .EqualFold() to parse urn prefixed UUIDs (#118) (574e687)

Add randomness pool mode for V4 UUID and NullUUID for SQL Scanners.

Choose a tag to compare

@pborman pborman released this 12 Jul 22:43

From Andrey Pechkurov:

Adds an optional randomness pool mode for Random (Version 4) UUID generation. The pool contains random bytes read from the random number generator on demand in batches. Enabling the pool may improve the UUID generation throughput significantly.

Since the pool is stored on the Go heap, this feature may be a bad fit for security sensitive applications. That's why it's implemented as an opt-in feature.

From Samuel Roth:

Added support for NullUUID

A NullUUID can be marked not valid (i.e., null) for use with JSON and the database/sql/driver.Scanner interfaces.

Add NewString()

Choose a tag to compare

@pborman pborman released this 22 Jan 18:22
bfb86fa

This release introduces the NewString() function which is the equivalent of uuid.New().String().

Syntactic cleanup

Choose a tag to compare

@pborman pborman released this 15 Jan 00:29
b5d0d36

There are no code changes. A missing period was add to a godoc comment and the linter was told to not complain that the results of hash.Write() are ignored (the function cannot fail)

Further error optimizations

Choose a tag to compare

@pborman pborman released this 04 Jan 19:19
85223fa

Do not allocate memory for errors (it is only one word)

Optimize error reporting

Choose a tag to compare

@pborman pborman released this 30 Dec 19:40
edef28d

Optimize length of time it takes to discover an input is bad by no longer using fmt.Errorf, which is quite slow. It now uses a custom error type that formats the string when the Error method is called rather than when generating the error.

Minor fixes

Choose a tag to compare

@pborman pborman released this 28 Aug 21:20
0e4e311

This release contains

  • Allow concurrent, re-creatable usage #44 by trabetti was merged on Apr 16, 2019
  • Fix race in NewUUID() #64 by AstolfoKawaii was merged on Jul 2, 2020
  • Minor formatting and typo fixes