direct URL dependencies are never outdated #6396
Merged
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.
I had intended just to tidy up a couple of places that missed the opportunity to use
package.is_direct_origin()
, but in doing so I found one that ought to do that - and that missed "url" source type.If a requirement specifies a direct URL, then that doesn't become outdated just because a newer version of the same package happens to be available in a repository.
(Or anyway if it does, then the same ought to apply to other direct-origin types, the url source type is not special)