[release/1.1] Update vulnerable regex versions and fix compilation errors #6083
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
onalante-msft
force-pushed
the
threadlocal-1.1
branch
from
1b83f71
to
46b961d
Compare
Also remove executable bits on code files.
onalante-msft
requested review from
varunpuranik,
arsing,
gordonwang0 and
bilalsellak
arsing
requested changes
Feb 4, 2022
arsing
previously approved these changes
Feb 4, 2022
|
Not sure why the review was dismissed, sorry. |
arsing
approved these changes
Feb 4, 2022
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.
Component governance identified a vulnerability in thread_local, which
was a transitive dependency brought in by older regex versions.
This has the additional benefit of unifying our regex dependency
versions.
RUSTSEC advisory: https://rustsec.org/advisories/RUSTSEC-2022-0006.html
Azure IoT Edge PR checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines and Best Practices
Testing Guidelines