build: Update dependencies with known vulnerabilities #1294
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* https://rustsec.org/advisories/RUSTSEC-2020-0059 * https://rustsec.org/advisories/RUSTSEC-2020-0060 * https://rustsec.org/advisories/RUSTSEC-2020-0091 * https://rustsec.org/advisories/RUSTSEC-2021-0003 * https://rustsec.org/advisories/RUSTSEC-2021-0023 * https://rustsec.org/advisories/RUSTSEC-2021-0072 * https://rustsec.org/advisories/RUSTSEC-2021-0078 * https://rustsec.org/advisories/RUSTSEC-2021-0079
jan-auer
changed the title
jan-auer
commented
Jun 9, 2022
| @@ -707,31 +707,33 @@ THd+9FBxiHLGXNKhG/FRSyREXEt+NyYIf/0cyByc9tNksat794ddUqnLOg0vwSkv | |||
| assert_annotated_snapshot!(data); | |||
| } | |||
|
|
|||
| macro_rules! sanitize_credit_card_within_value_test { | |||
There was a problem hiding this comment.
insta has changed the way it infers snapshot names. Before, it used the thread name from cargo test, which was set to the function. Since that was too brittle, it now uses the name of the function where insta::assert_* is called.
To keep the snapshot file names the same, we now use a macro rather than a subfunction.
jjbayer
approved these changes
Jun 9, 2022
jan-auer
added a commit
that referenced
this pull request
Jun 9, 2022
* master: ref(metrics): Stop logging relative bucket size (#1302) fix(metrics): Rename misnamed aggregator option (#1298) fix(server): Avoid a panic in the Sentry middleware (#1301) build: Update dependencies with known vulnerabilities (#1294) fix(metrics): Stop logging statsd metric per project key (#1295) feat(metrics): Limits on bucketing cost in aggregator [INGEST-1132] (#1287) fix(metrics): Track memory footprint more accurately (#1288) build(deps): Bump dependencies (#1293) feat(aws): Add relay-aws-extension crate which implements AWS extension as an actor (#1277) fix(meta): Update codeowners for the release actions (#1286) feat(metrics): Track memory footprint of metrics buckets (#1284)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrades dependencies in Cargo.lock and direct dependencies that are
marked with CVEs. There are still a few CVEs remaining that cannot be
updated easily as they require more extensive changes in the code base.
Since this PR contains many upgrades, all other dependency upgrades that
may carry code changes are left for a later point.
Fixed errors:
Remaining errors:
Allowed warnings, since these only mark unmaintained crates without known vulnerabilities:
#skip-changelog