Repository navigation
Update actions/setup-java action to v6 - #81
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
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
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 PR contains the following updates:
v5→v6Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/setup-java
v6.3.0Compare Source
Behavior change: Java problem matcher is now opt-in
Starting with v6.3.0,
setup-javano longer registers the Java problem matcher by default (#1326, fixes #1322). Java compiler warnings, compiler errors, and uncaught exceptions are no longer turned into annotations on pull request diffs unless you opt in.To keep annotations, set
problem-matcher: true:Compiler output still appears in the build logs, and compilation errors still fail the build. Only annotations are affected.
Why: inline annotations cluttered pull request reviews, and GitHub Actions caps annotations at 10 errors, 10 warnings, and 10 notices per step, and 50 per job. Larger Java builds therefore showed only a truncated subset of their diagnostics as annotations. See Java problem matcher (compiler annotations).
What's Changed
Full Changelog: actions/setup-java@v6.2.0...v6.3.0
v6.2.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/setup-java@v6.1.0...v6.2.0
v6.1.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/setup-java@v6.0.1...v6.1.0
v6.0.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/setup-java@v6.0.0...v6.0.1
v6.0.0Compare Source
What's Changed
18.0.1.1by @brunoborges in #1092New Contributors
Full Changelog: actions/setup-java@v5.7.0...v6.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.