Bump ramsey/uuid from 4.2.3 to 4.7.3

[dependabot]

Bumps ramsey/uuid from 4.2.3 to 4.7.3.

Release notes

Sourced from ramsey/uuid's releases.

4.7.3

Fixed

• The original 4.7.2 tag accidentally pointed to a commit in the 5.x branch. I have replaced the 4.7.2 tag with a new tag that points to the correct commit, but I am creating this tag to help notify users and automated processes who might have already updated to the bad 4.7.2 tag (#487).

4.7.2

Fixed

• Amend Psalm assertion syntax on Uuid::isValid() to prevent incorrect type inference (#486).
• Re-tagged with the correct commit hash, since the first tag was pointing to a commit in the 5.x branch (#487).

4.7.1

Fixed

• Allow the use of ramsey/collection ^2.0 with ramsey/uuid.

4.7.0

Added

• Add Uuid::fromHexadecimal() and UuidFactory::fromHexadecimal(). These methods are not required by the interfaces.

Fixed

• Ignore MAC addresses consisting of all zeroes (i.e., 00:00:00:00:00:00).

4.6.0

Added

• Add support for version 8, custom UUIDs, as defined in draft-ietf-uuidrev-rfc4122bis-00, section 5.8. While still an Internet-Draft, version 8 is stable and unlikely to change in any way that breaks compatibility.
  • Use Ramsey\Uuid\Uuid::uuid8() to generate version 8 UUIDs.
  • Version 8 UUIDs are of type Ramsey\Uuid\Rfc4122\UuidV8.
  • The constant Ramsey\Uuid\Uuid::UUID_TYPE_CUSTOM exists for version 8 UUIDs.

Fixed

• Ensure monotonicity of version 7 UUIDs.

4.5.1

Fixed

• Update RFC 4122 validator to recognize version 6 and 7 UUIDs.

4.5.0

Added

• Promote version 6, reordered time UUIDs from the Nonstandard namespace to the Rfc4122 namespace. Version 6 UUIDs are defined in [New UUID Formats, section 5.1][version6]. While still an Internet-Draft version 6 is stable and unlikely to change in any way that breaks compatibility.
• Add support for version 7, Unix Epoch time UUIDs, as defined in [New UUID Formats, section 5.2][version7]. While still an Internet-Draft, version 7 is stable and unlikely to change in any way that breaks compatibility.

... (truncated)

Changelog

Sourced from ramsey/uuid's changelog.

4.7.3 - 2023-01-12

Fixed

• The original 4.7.2 tag accidentally pointed to a commit in the 5.x branch. I have replaced the 4.7.2 tag with a new tag that points to the correct commit, but I am creating this tag to help notify users and automated processes who might have already updated to the bad 4.7.2 tag.

4.7.2 - 2023-01-12

Fixed

• Amend Psalm assertion syntax on Uuid::isValid() to prevent incorrect type inference (#486).
• Re-tagged with the correct commit hash, since the first tag was pointing to a commit in the 5.x branch.

4.7.1 - 2022-12-31

Fixed

• Allow the use of ramsey/collection ^2.0 with ramsey/uuid.

4.7.0 - 2022-12-19

Added

• Add Uuid::fromHexadecimal() and UuidFactory::fromHexadecimal(). These methods are not required by the interfaces.

Fixed

• Ignore MAC addresses consisting of all zeroes (i.e., 00:00:00:00:00:00).

4.6.0 - 2022-11-05

Added

• Add support for version 8, Unix Epoch time UUIDs, as defined in [draft-ietf-uuidrev-rfc4122bis-00, section 5.8][version8]. While still an Internet-Draft, version 8 is stable and unlikely to change in any way that breaks compatibility.
  • Use Ramsey\Uuid\Uuid::uuid8() to generate version 8 UUIDs.
  • Version 8 UUIDs are of type Ramsey\Uuid\Rfc4122\UuidV8.
  • The constant Ramsey\Uuid\Uuid::UUID_TYPE_CUSTOM exists for version 8 UUIDs.

... (truncated)

Commits

• 433b201 chore: prepare release 4.7.3
• c1de830 chore: prepare release 4.7.2 (again)
• 5b1cd8a chore: prepare release 4.7.2
• 4a14ce0 fix: Amends psalm assertion syntax on Uuid::isValid() to prevent incorrect ...
• 9077ba9 chore(deps): bump ridedott/merge-me-action from 2.10.40 to 2.10.42
• 616ae19 chore(deps): bump ridedott/merge-me-action from 2.10.39 to 2.10.40
• 1f9c6d7 Merge branch '3.x' into 4.x
• ad596eb chore: update year (#483)
• a1acf96 chore: prepare release 4.7.1
• e484aae chore: allow use of ramsey/collection ^2.0
• 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)