⬆️ Bump ramsey/uuid from 3.7.2 to 3.9.3

[dependabot-preview]

Bumps ramsey/uuid from 3.7.2 to 3.9.3.

Release notes

Sourced from ramsey/uuid's releases.

3.9.3

Fixed

• For v1 UUIDs, round down for timestamps so that microseconds do not bump the timestamp to the next second.

  As an example, consider the case of timestamp 1 with 600000 microseconds (1.600000). This is the first second after midnight on January 1, 1970, UTC. Previous versions of this library had a bug that would round this to 2, so the rendered time was 1970-01-01 00:00:02. This was incorrect. Despite having 600000 microseconds, the time should not round up to the next second. Rather, the time should be 1970-01-01 00:00:01.600000. Since this version of ramsey/uuid does not support microseconds, the microseconds are dropped, and the time is 1970-01-01 00:00:01. No rounding should occur.

3.9.2

Fixed

• Check whether files returned by /sys/class/net/*/address are readable before attempting to read them. This avoids a PHP warning that was being emitted on hosts that do not grant permission to read these files.

3.9.1

Fixed

• Fix RandomNodeProvider behavior on 32-bit systems. The RandomNodeProvider was converting a 6-byte string to a decimal number, which is a 48-bit, unsigned integer. This caused problems on 32-bit systems and has now been resolved.

3.9.0

Added

• Add function API as convenience. The functions are available in the Ramsey\Uuid namespace.
  • v1(int|string|null $node = null, int|null $clockSeq = null): string
  • v3(string|UuidInterface $ns, string $name): string
  • v4(): string
  • v5(string|UuidInterface $ns, string $name): string

Changed

• Use paragonie/random-lib instead of ircmaxell/random-lib. This is a non-breaking change.
• Use a high-strength generator by default, when using RandomLibAdapter. This is a non-breaking change.

Deprecated

These will be removed in ramsey/uuid version 4.0.0:

... (truncated)

Changelog

Sourced from ramsey/uuid's changelog.

[3.9.3] - 2020-02-20

Fixed

• For v1 UUIDs, round down for timestamps so that microseconds do not bump the timestamp to the next second.

  As an example, consider the case of timestamp 1 with 600000 microseconds (1.600000). This is the first second after midnight on January 1, 1970, UTC. Previous versions of this library had a bug that would round this to 2, so the rendered time was 1970-01-01 00:00:02. This was incorrect. Despite having 600000 microseconds, the time should not round up to the next second. Rather, the time should be 1970-01-01 00:00:01.600000. Since this version of ramsey/uuid does not support microseconds, the microseconds are dropped, and the time is 1970-01-01 00:00:01. No rounding should occur.

[3.9.2] - 2019-12-17

Fixed

• Check whether files returned by /sys/class/net/*/address are readable before attempting to read them. This avoids a PHP warning that was being emitted on hosts that do not grant permission to read these files.

[3.9.1] - 2019-12-01

Fixed

• Fix RandomNodeProvider behavior on 32-bit systems. The RandomNodeProvider was converting a 6-byte string to a decimal number, which is a 48-bit, unsigned integer. This caused problems on 32-bit systems and has now been resolved.

[3.9.0] - 2019-11-30

Added

• Add function API as convenience. The functions are available in the Ramsey\Uuid namespace.
  • v1(int|string|null $node = null, int|null $clockSeq = null): string
  • v3(string|UuidInterface $ns, string $name): string
  • v4(): string
  • v5(string|UuidInterface $ns, string $name): string

Changed

• Use paragonie/random-lib instead of ircmaxell/random-lib. This is a

... (truncated)

Commits

• 7e1633a Skip tests on 32-bit systems
• e901238 Fix rounding bug in timestamp for v1 UUIDs
• e535e89 Fix typo
• eb1645b Add behavior test for TimestampFirstCombCodec
• da6fcde Add tests to ensure consistent behavior from 3.x to 4.x
• f6da4ae Bump copyright year to 2020
• 7779489 Fix CHANGELOG links
• 21a981c Update CHANGELOG for 3.9.2 release
• b39ec78 Check whether sysfs is readable before attempting to read it
• ed4223e Add scripts to build Docker images for alternate CPU arch testing
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)