437: GitHub actions/fmt r=KodrAus a=kinggoesgaming

**I'm submitting a(n)** other

# Description
Moves `cargo fmt` step to Github Actions

# Motivation
Overall Github Actions provide more flexibility for us. 
But since Actions are still in beta, starting with fmt is a relatively safe start


Co-authored-by: Hunar Roop Kahlon <[email protected]>

(don't edit files on the go on iPhone, really doesnt work)

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Currently it is broken and we can probably just leave with manually checking clippy output

439: Introduce Clippy Github Actions r=Dylan-DPC a=kinggoesgaming

**I'm submitting a(n)** other

# Description
Moves clippy tests over to Github Actions

Co-authored-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Updates the requirements on [md5](https://github.com/stainless-steel/md5) to permit the latest version.
- [Release notes](https://github.com/stainless-steel/md5/releases)
- [Commits](https://github.com/stainless-steel/md5/commits)

Signed-off-by: dependabot-preview[bot] <[email protected]>

442: Update md5 requirement from 0.6 to 0.7 r=kinggoesgaming a=dependabot-preview[bot]

Updates the requirements on [md5](https://github.com/stainless-steel/md5) to permit the latest version.
<details>
<summary>Commits</summary>

- See full diff in [compare view](https://github.com/stainless-steel/md5/commits)
</details>
<br />

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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](https://app.dependabot.com):
- 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)



</details>

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>

Reduces the number of dependencies.

Co-Authored-By: Hunar Roop Kahlon <[email protected]>

Co-Authored-By: Hunar Roop Kahlon <[email protected]>

Co-Authored-By: Hunar Roop Kahlon <[email protected]>

447: Use getrandom crate for uuid r=kinggoesgaming a=ammgws

<!--
    If this PR is a breaking change, ensure that you are opening it against 
    the `breaking` branch.  If the pull request is incomplete, prepend the Title with WIP: 
-->

**I'm submitting a(n)** other

# Description

Use `getrandom` crate directly instead of `rand` for generating UUIDs using v4.

# Motivation

Reduce the number of dependencies used by the crate.

Running the example in the README: 
- Before (10): c2-chacha, cfg-if, getrandom, libc, ppv-lite86, rand, rand_chacha, rand_core, rand_hc, wasi  
- After (4): cfg-if, getrandom, libc, wasi

# Tests
<!-- How are these changes tested? -->
`cargo test` locally and test usage in a simple program.

# Related Issue(s)

# Other

Wasn't sure whether I should bump the version here or not.


Co-authored-by: Jason Nader <[email protected]>
Co-authored-by: Jason <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

449: make `Uuid::from_guid` infallible r=Dylan-DPC a=kinggoesgaming

closes #446

Co-authored-by: Hunar Roop Kahlon <[email protected]>

454: Fix unspecified direct object in README r=kinggoesgaming a=cedric-h

<!--
    If this PR is a breaking change, ensure that you are opening it against 
    the `breaking` branch.  If the pull request is incomplete, prepend the Title with WIP: 
-->

**I'm submitting a grammar fix for the README**


# Description
Previously, the README contained "They are particularly useful in distributed systems, *though can be used*..."
To a native speaker, this sounds a little strange, whereas "They are particularly useful in distributed systems, though **they** can be used..." is clearer and more grammatically correct.

# Motivation
I'd like to make the README easier to understand

# Tests
I read it out loud and it sounded better and made more sense.

# Related Issue(s)
N/A

Co-authored-by: Cedric Hutchings <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

When the wasm32 architecture is used with WASI, md5, getrandom, and sha1
are all available, so V3, V4, and V5 can be enabled.

Create initial ci file

Github Actions CI part 2

The rand crate changed its trait names, so these docs were referencing a
trait that doesn't exist in the current version of rand. Change to be a
bit more vague to avoid this getting out of date again.

Also "use rand instead" wasn't very clear because "rand" doesn't contain
something clearly equivalent like `get_uuid_v4`. To be clearer, add a
reference to the `Builder::from_bytes` function in this crate.

490: remove appveyor from bors r=kinggoesgaming a=kinggoesgaming

I missed to do this while working on #487, as now appveyor has been unlinked


Co-authored-by: Hunar Roop Kahlon <[email protected]>

489: Clarify documentation around the relation to the rand crate r=kinggoesgaming a=carols10cents

**I'm submitting a(n)** other - documentation improvement

# Description

The rand crate changed its trait names, so these docs were referencing a
trait that doesn't exist in the current version of rand. Change to be a
bit more vague to avoid this getting out of date again.

Also "use rand instead" wasn't very clear because "rand" doesn't contain
something clearly equivalent like `get_uuid_v4`. To be clearer, add a
reference to the `Builder::from_bytes` function in this crate.

# Motivation

It took me a few minutes to figure out what this documentation was saying, and I'd like to save someone else those few minutes in the future.

# Tests

N/A

# Related Issue(s)

None


Co-authored-by: Carol (Nichols || Goulding) <[email protected]>
Co-authored-by: Carol (Nichols || Goulding) <[email protected]>

478: Remove dependency on serde_derive r=kinggoesgaming a=coolreader18

<!--
    If this PR is a breaking change, ensure that you are opening it against 
    the `breaking` branch.  If the pull request is incomplete, prepend the Title with WIP: 
-->

**I'm submitting a(n)** other


# Description
Remove the `serde_derive` feature from the `serde` dependency.
# Motivation
`serde_derive` is a pretty heavy dependency that adds a lot to compile times; as it's not used in this crate outside of tests, I figured it would be ok to remove it.
# Tests
<!-- How are these changes tested? -->
n/a
# Related Issue(s)
#408 ?

Co-authored-by: Noah <[email protected]>
Co-authored-by: Hunar Roop Kahlon <[email protected]>

491: remove fmt from travis r=kinggoesgaming a=kinggoesgaming




Co-authored-by: Hunar Roop Kahlon <[email protected]>

477: Add wasm32-wasi support for V3, V4, and V5 r=kinggoesgaming a=sunfishcode

**I'm submitting a(n)** feature

# Description

When the wasm32 architecture is used with WASI, md5, getrandom, and sha1
are all available, so V3, V4, and V5 can be enabled.

# Motivation

I'm porting an application that uses `uuid` to WASI and would like to add support.

# Tests

`cargo test --target=wasm32-wasi --all-features` passes.

Co-authored-by: Dan Gohman <[email protected]>
Co-authored-by: Hunar Roop Kahlon <[email protected]>

471: fix documentation with incorrect links for consts in v3 r=kinggoesgaming a=woshilapin

<!--
    If this PR is a breaking change, ensure that you are opening it against 
    the `breaking` branch.  If the pull request is incomplete, prepend the Title with WIP: 
-->

**I'm submitting a documentation fix**

# Description
Incorrect links in the documentation of `Uuid::new_v3()` to the `const` for namespaces.

# Motivation
Fix the documentation.

# Tests
I built locally and open the documentation. It works.

# Related Issue(s)


Co-authored-by: Jean SIMARD <[email protected]>
Co-authored-by: Hunar Roop Kahlon <[email protected]>

…o the-transparency-report

Signed-off-by: Hunar Roop Kahlon <[email protected]>

468: make uuid structs repr(transparent) r=KodrAus a=kinggoesgaming

**I'm submitting a(n)** feature

# Description
Make the following structs `#[repr(transparent)]`:
* `Uuid`
* `Hyphenated`
* `HyphenatedRef`
* `Simple`
* `SimpleRef`
* `Urn`
* `UrnRef`

# Tests
Tests should pass as is

# Related Issue(s)
closes #463 

Co-authored-by: Hunar Roop Kahlon <[email protected]>
Co-authored-by: Hunar Roop Kahlon <[email protected]>

467: Fix example in README.md r=kinggoesgaming a=heckad

Fix


Co-authored-by: Kazantcev Andrey <[email protected]>
Co-authored-by: Hunar Roop Kahlon <[email protected]>

Signed off by: fossabot <[email protected]>

492: Add license scan report and status r=kinggoesgaming a=fossabot

Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

- [CircleCI](https://docs.fossa.com/docs/circleci)
- [TravisCI](https://docs.fossa.com/docs/travisci)
- [Jenkins](https://github.com/fossas/fossa-jenkins-plugin)
- [Other](https://github.com/fossas/fossa-cli)

Co-authored-by: fossabot <[email protected]>

Signed-off-by: Hunar Roop Kahlon <[email protected]>

…builder