| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
Code Climate has analyzed commit 14e5af4 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (80% is the threshold). This pull request will bring the total coverage in the repository to 98.9% (0.0% change). View more on Code Climate. |
Sorry, something went wrong.
|
I probably can't do much about the CI failure
|
Sorry, something went wrong.
|
Makes perfect sense, less dependencies is always good 👍 CI failure is not critical, it couldn't upload the report, not a big deal. |
Sorry, something went wrong.
|
Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Why
The uuid gem is archived on GitHub since Jan 1, 2024: https://github.com/assaf/uuid
Although one might consider it feature complete and no longer require any updates (in fact, the last update was made 5 years ago), I would still consider it a risk. Its transitive dependencies macaddr and systemu were updated in 2019 and 2015 respectively.
The change removes 3 dependencies: uuid » macaddr » systemu.
How
Ruby already has a way to generate UUIDs via SecureRandom. It is v4 (compared to v1 implemented by the uuid gem), but for Allure purposes it should make no difference. Another option is PRNG version implemented in Random#uuid_v4 and Random#uuid_v7, but it requires an instance of PRNG, and so more code changes.