Allow ramsey/uuid v4.x

[enumag]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 634

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 67.722%

---

Totals
Change from base Build 616:	0.0%
Covered Lines:	3231
Relevant Lines:	4771

---

💛 - Coveralls

[prolic]

@enumag Why not pin to 4.0 directly? I didn't check this new major release so far. What's the difference?

[prolic]

Looking at https://github.com/ramsey/uuid/releases/tag/4.0.0, I think pinning to 4.0 is the way to go. Thoughts?

[enumag]

I think that locking it at v4.0 might make sense when solving #119 since that might require using more of ramsey's features. But until then ramsey/uuid is just a minor dependency for us and the bc breaks don't affect us. Locking it at v4.0 needlessly would only cause unnecessary dependency conflicts for our users who might have dependencies on ramsey/uuid through some other libraries. It kinda depends on when you're planning on working on #119 but since you're busy lately I'm treating it as something that may or may not happen soon so I'm not including it into my considerations here.

[prolic]

I tried creating Guid's using 4.0 of this ramsey-lib and ended up creating an issue: ramsey/uuid#306

[prolic]

solved via prooph/event-store#387