build: marking dependencies (8) non-required#1472
Merged
Conversation
blakeli0
approved these changes
Jun 29, 2022
chingor13
approved these changes
Jun 29, 2022
Contributor
chingor13
left a comment
chingor13
left a comment
There was a problem hiding this comment.
Probably want to merge this as a build because this PR title will propagate to the PR opened in each repository
parthea
changed the title
Member
Author
|
Merged this with "build:" prefix. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Because our dependency tree do not changes between Java language versions, there's no point to require the dependency check each version. Keeping "dependencies (11)" intact.