Assigned RUSTSEC-2020-0136 to toolshed, RUSTSEC-2021-0015 to calamine, RUSTSEC-2020-0137 to lever, RUSTSEC-2020-0138 to lexer

.duplicate-id-guard

@@ -1,3 +1,3 @@
 This file causes merge conflicts if two ID assignment jobs run concurrently.
 This prevents duplicate ID assignment due to a race between those jobs.
-de1acbaba29cc19b4f73514fc9a4a35cf8123dba04b1ef9f6e657d8bb4aba9bf  -
+0843772da74b2bdd501aec16ad17ac2ce903efeea1bfea1833387c3ca5201b68  -

crates/calamine/RUSTSEC-2021-0015.md

@@ -1,6 +1,6 @@
 ```toml
 [advisory]
-id = "RUSTSEC-0000-0000"
+id = "RUSTSEC-2021-0015"
 package = "calamine"
 date = "2021-01-06"
 url = "https://github.com/tafia/calamine/issues/199"

crates/lever/RUSTSEC-2020-0137.md

@@ -1,6 +1,6 @@
 ```toml
 [advisory]
-id = "RUSTSEC-0000-0000"
+id = "RUSTSEC-2020-0137"
 package = "lever"
 date = "2020-11-10"
 url = "https://github.com/vertexclique/lever/issues/15"

crates/lexer/RUSTSEC-2020-0138.md

@@ -1,6 +1,6 @@
 ```toml
 [advisory]
-id = "RUSTSEC-0000-0000"
+id = "RUSTSEC-2020-0138"
 package = "lexer"
 date = "2020-11-10"
 url = "https://gitlab.com/nathanfaucett/rs-lexer/-/issues/2"
@@ -18,4 +18,4 @@ Since matching on the public enum `ReaderResult<T, E>` provides access to `&T` &
 allowing data race to a non-Sync type `T` or `E`.
 This can result in a memory corruption when multiple threads concurrently access `&T` or `&E`.
 
-Suggested fix for the bug is change the trait bounds imposed on `T` & `E` to be `T: Sync, E: Sync`.
+Suggested fix for the bug is change the trait bounds imposed on `T` & `E` to be `T: Sync, E: Sync`.

crates/toolshed/RUSTSEC-2020-0136.md

@@ -1,6 +1,6 @@
 ```toml
 [advisory]
-id = "RUSTSEC-0000-0000"
+id = "RUSTSEC-2020-0136"
 package = "toolshed"
 date = "2020-11-15"
 url = "https://github.com/ratel-rust/toolshed/issues/12"