fix: use poetry-lock file as a target file for poetry project #143
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
|
|
1 task
|
🎉 |
|
🎉 This PR is included in version 1.19.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 does this PR do?
As a part of this PR we we will pass
poetry.lockfile to this plugin as opposed topyproject.toml. This is becausepyproject.tomlis not a reliable manifest file (see https://github.com/snyk/snyk/issues/1802) and therefore we need to usepoetry.lockas a traget file. This is a breaking changeNew published version has to be integrated into snyk/cli#1879
How should this be manually tested?
What are the relevant tickets?
LOKI-280