uuid6/prototypes

Call for Draft 03 Prototype Testing

kyzer-davis opened this issue · 6 comments

@jdknezek, @daegalus, @chrylis, @mikemix, @kurttheviking, @sprql, @kjmph, @MatrixAI, @kripod, @karwa, @mareek, @oittaa, @jakwings, @fabiolimace, @LiosK, @theckman

Draft 03 Announcement

  • Draft 03 has been submitted to the IETF!
  • Draft 03 has some changes to UUIDv7 which may break current Draft 01/02 implementations so please confirm compatibility with Draft 03.
  • If there is any feedback found during review or while updating the prototype implementation; please contribute to one of the existing Discussion Threads (where possible.)
  • Else please open a PR to update the table in this document to reflect Draft 03 compatibility.

The Official Draft 03 can be found at the following locations:


Thanks all!

I’ve just released @kripod/uuidv7 v0.3 on npm, which supports the latest draft of the specification. Thank you for notifying me about its release and cheers for putting it together 🙌

Thanks for pushing this forward. I've also updated my test libraries oittaa/uuid-php and oittaa/uuid6-python.

thx for the heads up, might take me a bit to update, but ill get to it soon.

sprql commented

I’ve just released @sprql/uuid7-ruby v0.2.0 ruby gem, which based the latest draft of the specification. Thank you for notifying me.

I just pushed up changes to catch me up to Draft 3, and added a UUIDv8, opened a PR with the changes. #29

kjmph commented

I updated my public Postgres gist; note, as I was used to microsecond precision, I also added UUID v8 for those looking to preserve that capability.