fix: ensure that package exists in affected property
#1055
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
|
This unbreaks #958 |
G-Rath
force-pushed
the
generators/ensure-package-present
branch
from
6f486eb
to
53e3404
Compare
G-Rath
force-pushed
the
generators/ensure-package-present
branch
from
53e3404
to
8a4f342
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1055 +/- ##
=======================================
Coverage ? 65.30%
=======================================
Files ? 150
Lines ? 12525
Branches ? 0
=======================================
Hits ? 8179
Misses ? 3882
Partials ? 464 ☔ View full report in Codecov by Sentry. |
hogo6002
approved these changes
Jun 24, 2024
another-rex
approved these changes
Jun 24, 2024
cuixq
approved these changes
Jun 25, 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.
This has always been allowed by the spec but now there's at least one real-world advisory in the Debian database like this which causes it to error.