Closed andreeaflorescu closed 2 years ago
nit: we could also update the docs so that they point to the latest version published. It might actually be a good idea to replace the hardcoded values with v${LATEST} everywhere as we already do and explain here.
I've updated the README as well and added a note that the version specified there might not be the latest one. We might forget to update it from time to time.
Summary of the PR
This version adds some tooling for fuzzing and updated to Rust 1.63.0.
Requirements
Before submitting your PR, please make sure you addressed the following requirements:
git commit -s
), and the commit message has max 60 characters for the summary and max 75 characters for each description line.unsafe
code is properly documented.