What's Changed

• Update All (major) by @renovate[bot] in #143
• Add support for loose validation by @DPDmancul in #145

New Contributors

• @DPDmancul made their first contribution in #145

Full Changelog: 4.5.3...4.6.0

• Add explicit 128-bit hexadecimal format validators: Uuid.isValidUUIDFormat(...), UuidValue.validateFormat(), UuidValidation.isValidUUIDFormat(...), and UuidValidation.isValidFormatOrThrow(...). (thanks @DPDmancul)
• Add UuidValue.withFormatValidation(...) for values whose UUID version and variant bits should not be checked. (thanks @DPDmancul)
• Add Uuid.parseHex128(...), Uuid.parseHex128AsByteList(...), UuidParsing.parseHex128(...), and UuidParsing.parseHex128AsByteList(...). (thanks @DPDmancul)
• Require exact single-line 8-4-4-4-12 or 32-character hexadecimal input and exactly 16 bytes during format validation.
• Expose the existing noDashes parsing option through the public Uuid parse methods.

What's Changed

• Update actions/checkout action to v6 by @renovate[bot] in #138
• Add binary input support for UUIDv5 (RFC 4122/9562 compliant) by @ljanecek in #137
• fix: Remove the experimental annotation from the UuidValue class by @marcelomendoncasoares in #141

New Contributors

• @ljanecek made their first contribution in #137
• @marcelomendoncasoares made their first contribution in #141

Full Changelog: 4.5.2...4.5.3

• Remove experimental flag on UUIDValue and remote meta dependency. (thanks @marcelomendoncasoares)
• Add binary support to UUIDv5 (thanks @ljanecek)

What's Changed

• Fix validation to allow MAX UUID (FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF) as it is valid.
• Add strictRFC9562 and deprecate strictRFC4122 to facilitate a rename. This will be remove in v5
• Remove sprintf dependency by @julemand101 in #132
• Add const constructor to CryptoRNG class by @4akloon in #134
• update docs for v5 by @JarvanMo in #136
• Update All (major) by @renovate[bot] in #129

New Contributors

• @4akloon made their first contribution in #134
• @JarvanMo made their first contribution in #136

Full Changelog: 4.5.1...4.5.2

• Fix validation to allow MAX UUID (FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF) as it is valid.
• Add strictRFC9562 and deprecate strictRFC4122 to facilitate a rename. This will be remove in v5

Changelog

• Add UuidValue.fromNamespace to let you make constant variants of the namespace, as due to language limitations on Enums, Namespace.*.uuidValue can't be constant.
• Added isV#(), isNil(), and isMax() functions to UuidValue for matching Dart standards.

Full Changelog: 4.5.0...4.5.1

• Add UuidValue.fromNamespace to let you make constant variants of the namespace, as due to language limitations on Enums, Namespace.*.uuidValue can't be constant.
• Added isV#(), isNil(), and isMax() functions to UuidValue for matching Dart standards.

Changelog

• Change to CryptoRNG by default, you will now need to use MathRNG explicitly if you want speed over security. (thanks @Rexios80)
  • This also works around a regression in the Dart SDK on WASM targets: dart-lang/sdk#56609
• Deprecate the use of Uuid.NAMESPACE* and UuidV5.NAMESPACE, and switch to using a proper const enum for this. (thanks @bymoye)
  • These will be removed once sufficient time has been made for the deprecation notice to be seen. Most likely v5.0.
  • Please use the new Namespace enum in enums.dart.
• Re-add Uuid.NAMESPACE* and UuidV5.NAMESPACE in order to give deprecation time.
• Add missing MAX UUID option from RFC9562
• Add bytes getter to Namespace enum.
• [PARTIAL BREAKING CHANGE] Namespace is now an enum, and the entries are now of the Namespace type. They all have a value function to return the internal string

What's Changed

• remove multiple individually defined Namespaces and use enumerations instead by @bymoye in #122
• Always use CryptoRNG as the default by @Rexios80 in #126

New Contributors

• @bymoye made their first contribution in #122
• @Rexios80 made their first contribution in #126

Full Changelog: 4.4.2...4.5.0

• Change to CryptoRNG by default, you will now need to use MathRNG explicitly if you want speed over security. (thanks @Rexios80)
  • This also works around a regression in the Dart SDK on WASM targets: https://github.com/dart-lang/sdk/issues/56609
• Deprecate the use of Uuid.NAMESPACE* and UuidV5.NAMESPACE, and switch to using a proper const enum for this. (thanks @bymoye)
  • These will be removed once sufficient time has been made for the deprecation notice to be seen. Most likely v5.0.
  • Please use the new Namespace enum in enums.dart.
  • These will be removed in v5
• Re-add Uuid.NAMESPACE* and UuidV5.NAMESPACE in order to give deprecation time.
• Add missing MAX UUID option from RFC9562
• Add bytes getter to Namespace enum.
• [PARTIAL BREAKING CHANGE] Namespace is now an enum, and the entries are now of the Namespace type. They all have a value function to return the internal string

What's Changed

• fix: downgrade meta dependency by @techouse in #121

New Contributors

• @techouse made their first contribution in #121

Full Changelog: 4.4.1...4.4.2

• Revert meta depenency version upgrade, was breaking flutter_test. (thanks @techouse)

v4.4.1

• Fix UUIDv1 to use millisecondsSinceEpoch instead of microsecondsSinceEpoch. Matches UUIDv6 and passes vector tests. (#119)

What's Changed

• Update renovate.json by @daegalus in #114
• Update All (major) by @renovate in #115
• Update dependency lints to v4 by @renovate in #116

New Contributors

• @renovate made their first contribution in #115

Full Changelog: 4.4.0...4.4.1

• Fix UUIDv1 to use millisecondsSinceEpoch instead of microsecondsSinceEpoch. Matches UUIDv6 and passes vector tests.

• Fix MathRNG with Seed being recreated on each use, generating the same list of bytes. (thanks @showband)
• Fix UUIDv5 UTF8 inconsistencies. (thanks @vjamrich)
• Use static state storage for random number generator to prevent MathRNG issue.
• Replace V1, v6, V7, V8 MathRNG preventively, the issue didn't exhibit there due to other factors in the UUID generation (primarily time, and clockseq)

What's Changed

• fixed MathRNG - it now uses the initial seed properly by @showband in #109
• Fix V5 UUID inconsistencies when using UTF-8 characters by @vjamrich in #112

New Contributors

• @showband made their first contribution in #109
• @vjamrich made their first contribution in #112

Full Changelog: 4.3.3...4.4.0

• Fix MathRNG with Seed being recreated on each use, generating the same list of bytes. (thanks @showband)
• Fix UUIDv5 UTF8 inconsistencies. (thanks @vjamrich)
• Use static state storage for random number generator to prevent MathRNG issue.
• Replace V1, v6, V7, V8 MathRNG preventively, the issue didn't exhibit there due to other factors in the UUID generation (primarily time, and clockseq)

v4.3.3

• Fix UUIDv7 in Javascript
  • Using bitshifts on anything over 32bits get truncated. Switched to a more naive solution for now. Hopefully dart2wasm fixes things.
• Remove unnecessary _randomData() functions
• Add fixnum package to handle issues in v6, time, and javascript.

Full Changelog: 4.3.2...4.3.3

• Fix UUIDv7 in Javascript
  • Using bitshifts on anything over 32bits get truncated. Switched to a more naive solution for now. Hopefully dart2wasm fixes things.
• Remove unnecessary _randomData() functions
• Add fixnum package to handle issues in v6, time, and javascript.

• Added toFormattedString() to UuidValue to handle cases where the UUID used has no hyphens but you wnt them for output.
• Changed constraint for meta to 1.10.0 to not conflict with flutter_test

Full Changelog: 4.3.1...4.3.2

• Added toFormattedString() to UuidValue to handle cases where the UUID used has no hyphens but you wnt them for output.
• Changed constraint for meta to 1.10.0 to not conflict with flutter_test

• Add additional optional parameters for parseing and validation for the new noDashes flag.

• Update SDK constraints to >= 3.0.0
• Update Meta package to 1.11.0
• [PARTIAL BREAKING CHANGE] Changing MathRNG implementation to use 4 nextints, instead of 16 for optimization to match CryptoRNG. This will affect regenerating the same UUID from the same seed.
  • If you need the old behavior, please use MathRNGDeprecated() instead.

• Fix CryptoRNG on Web generating a random number 0 always
• Add NoDashes support to the validator so that it validates UUIDs that don't have dashes but are otherwise valid.

• Lower meta dependency to 1.9.1 so that it is compatible with Flutter Stable 3.13

• [BREAKING CHANGE] Deprecate default/empty UuidValue constructor because it has a different behavior from the 3.x package version. (Thanks @davidmartos96)
  • Use UuidValue.fromString() instead, which has the same behavior. If you need to define a const UuidValue you can use UuidValue.raw(), but making sure the value is lowercase.
• Mark UuidValue as experimental with an annotation. (Thanks @Kaival-Patel)

• [BREAKING CHANGE] In order to enforce lowercase strings in UuidValue, I have made the default const constructor private, and added a fromString factory constructor. Please migrate any direct UuidValue() usage to UuidValue.fromString() or UuidValue.withValidation().

• toBytes on UuidValue now does not validate by default, but has the option validate that can be set to true if you need validation when calling it. (Thanks @Erhannis)

• [BREAKING CHANGE] Replacing UuidUtil rng functions with RNG classes.
  • UuidUtil.mathRNG() is replaced with MathRNG().generate().
  • UuidUtil.cryptoRNG() is replaced with CryptoRNG().generate().
  • Custom crypto implementations just need to implement the RNG abstract class.
  • namedArgs and positionalArgs have been removed from GlobalOptions
  • You may use LegacyRNG() if you need to use the old function style RNG.
• Fix a bug with the usage of Uint64List in Dart2js by not using it. (Thanks @hambergerpls)

• [BREAKING CHANGE] The Uuid class now takes a GlobalOptions class instead of a Map<String, dynamic>.
• Added options classes to eventually replace the Map parameter.
• [BREAKING CHANGE] Since v6,v7,v8 are new for 4.0, I have made it so they only take the new options class.
• Reworked the constructors, and moved state out of the classes. Const is now supported properly again
• Switched tests to use const Uuid to catch regressions.
• Set the options parameter in v1, v4, and v5 to deprecated.
• [BREAKING CHANGE] Make UuidValue properly const also
  • Can no longer run validation on the const variant.
  • Added UuidValue.withValidation() to handle this usecase, it can't be const.
  • If you need const and validation. Create the UuidValue with the UUID, then call the validate() function on it.

• Break up versions into individual objects that can be used standalone.
• No more colliding global states between versions
• Added UUID v6, v7, v8 from the new RFC.
• Add time, version, and variant functions to UuidValue

• Fixed parse to allow buffers larger than 16 bytes to be used. [Thanks @hoylen]

• Enable avoid_dynamic_calls linting and fix appropriately. (Thanks @devoncarew)

• Global options were incorrectly being ignored. #76 (Thanks @Skycoder42)
• V4 Global Options were incorrectly named. #76 (Thanks @Skycoder42)
• Global state was static, not per instance. #76 (Thanks @Skycoder42)
• Additional tests to make sure the above doesn't regress. #76 (Thanks @Skycoder42)

• isValidUUID now handles some Microsoft GUIDs better that only deviate in the Variant setting. (Thanks @FluentChange)
• Improve error output so that it better explains how to handle the above change in your code if you encounter it. (Thanks @FluentChange)
• Improve validation logic to better handle multiple validation cases, error output, and feedback to developers. (Thanks @FluentChange)

• [Experimental] Fixed UuidValue to properly check things are valid. (Thanks @FlorianUlivi)
• [Experimental] Added new constructors fromByteList and fromList to UuidValue
• [Experimental] Added == operator override and hashcode override. (Thanks @giorgiofran for suggestion)
• Added parseAsByteList to offer a direct output to Uint8List
• [Experimental][BREAKING CHANGE] Change toBytes in UuidValue to return Uint8List instead of List<int>
• [Experimental][BREAKING CHANGE] isValidUuid function signature has changed, now takes 2 optional parameters fromString and fromList that will do the appropriate validation on different sources.

• [Experimental] Add flags to UuidValue constructor and parse to disable validation of the UUID, primarily to allow Microsoft GUIDs to not break things.

• Fix RNG to not need shuffling and improve performance/memory usage (Thanks @julemand101)

• Release nullsafety version.

• [BREAKING CHANGE] Changed parse() to throw a FormatException instead of returning NIL uuids or partially handled UUIDs.
• Changed Uuid constructor to be constant, and adjusted all the code accordingly.
• New isValidUUID function for validating UUIDs.
• [BREAKING CHANGE] parse and unparse are now static functions.
• [Exprimental] Object version of the UUID instead of a string or list of bytes.

• Migrate package to null-safety, increase minimum SDK version to 2.12 (Thanks @simolus3)

v2.2.1 & v2.2.2

• Update pedantic analyzer options, fix linting issues, and increase SDK minimium to 2.2 to support set literals

• fix v1 clock high to properly ignore c and d variants. (fixes #47)
• update example

• Shuffle mathRNG bytes so that they don't generate duplicates. Will affect codes generated by a static seed.

• Remove new keyword where not needed. (forgot to rerun before releasing 2.0.3)

• Do some analyzer fixes and formatting/renaming.

• Merge fix for time precision loss in V1 time based UUIDs.

• Fix regression where CryptoRNG was default, moved back to MathRNG
• Added ability to set RNG globally to skip having to set it in every function call
• Allows you to set the v1 clock sequence, nodeID, and seed bytes to use cryptoRNG separately from globalRNG.

• Fixup the API to split out Buffer and Non-buffer usages.
• Switch to build in Random.secure() and remove custom AES implementation.
• Less dependencies.
• Docs
• Cleanup

• Fix SDK constraints to allow Dart 2.0 stable.

• Fix constants breaking in Dart 1.x, need to be backwards compatible.

• Fix constants to match Dart 2.0 spec

• Cleanup and prep for dart 2.0
• Has been stable for a long time, upgrading to 1.0 version

• Merged pull request to support crypto 2.0.0
• Support convert 2.0.0

• Merged pull request to upgrade crypto library to 1.0.0.

• Merged pull request for various updates and cleanup.

• Reverted back to custom AES implementation. Moved RNG methods to UuidUtil (import 'package:uuid/uuid_util.dart')
• Fixed a potential bug with custom RNG method passing and added more ways to pass in custom RNG functions.
• Cleaned up and refactored some stuff. Using only v1 is only 67kb of js, Using only v4 is 97kb. Using crypt v4 is 118kb. Using both v1 and non-crypto v4 is 126kb.
• Default RNG for v4 is now the mathRNG function. If you wish to use cryptoRNG, import UuidUtil and pass in cryptoRNG.
• Updated README.md with more examples and usages.
• Updated Tests.

• Changed initCipher location so that if you ever only use v1 UUIDs, you will get a very small Dart2JS output compared to v4 or v5 that do load it.

• Use Cipher base.dart, as I don't need entropy generators, and this allows me to merge client/server together again and fix many issues this caused.

• Fix import/library bug.

• Update pubspec to allow installation of the latest Cipher 0.7.

• Updated to latest Cipher at 0.6.0. This created a breaking change in the imports. Please make sure you update your code.
• Fixed problem when creating v4 UUIDs too fast, it would create duplicate UUIDs.

• Pegging cipher to 0.4.0 temporarily for browser support

• Using new version of cipher.

• Dart 1.0 Readiness
• Switched from custom AES to cipher package AES.

• Adjusting usage of constants.
• Fixing tests.

• Stupid typo on import.