feat(load.go): add warning on requirements.lock #12867
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
pull-request-size
bot
added
the
size/XS
Signed-off-by: Aaron U'Ren <aauren@users.noreply.github.com>
aauren
force-pushed
the
add_requirements.lock_warning
branch
from
8c186ae
to
29ab5c4
Compare
|
@gjenkins8 Are you still interested in this PR? |
robertsirc
approved these changes
Apr 12, 2024
mattfarina
approved these changes
May 15, 2024
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.
What this PR does / why we need it:
Adds a warning when
requirements.lockis used and the API version is notv1.Partial fix for: #12853 (full fix to come when this functionality is hopefully removed in v4)
Special notes for your reviewer:
FYI @gjenkins8
If applicable: