Update secure resolver proposal #476
Merged
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
dbadura
requested review from
akgalwas,
aszecowka,
crabtree,
franpog859,
janmedrek,
kfurgol,
Maladie,
PK85,
pkosiec,
Szymongib and
tgorgol
as code owners
dbadura
force-pushed
the
update-secure-resolver-proposal
branch
5 times, most recently
from
62e529a
to
ca4a6ba
Compare
dbadura
force-pushed
the
update-secure-resolver-proposal
branch
from
ca4a6ba
to
8015232
Compare
|
Probably we can use the directive on field, but we need to update |
As far as I know, we are now on 0.9.3 |
crabtree
reviewed
Nov 22, 2019
crabtree
approved these changes
Nov 22, 2019
DimitarPetrov
pushed a commit
to DimitarPetrov/compass
that referenced
this pull request
Aug 23, 2021
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.
Description
Changes proposed in this pull request:
Related issue(s)
See #419