Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update actions/setup-java action to v3.5.0 #16

Merged
merged 1 commit into from
Sep 16, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 8, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
actions/setup-java action minor v3.4.1 -> v3.5.0

Release Notes

actions/setup-java

v3.5.0

Compare Source

Add support for multiple jdks

In scope of this release we add support for multiple jdks. Customers can specify multiple versions of java through java-version input.

    steps:
      - uses: actions/setup-java@v3
        with:
          distribution: '<distribution>'
          java-version: |
            8
            11
            15
Besides, we added such changes as:

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@JavierSegoviaCordoba
Copy link
Member

There are no default requesters for this repo, is this intended?

@nomisRev nomisRev merged commit cf778ae into main Sep 16, 2022
@renovate renovate bot deleted the renovate/actions-setup-java-3.x branch September 16, 2022 12:58
@nomisRev
Copy link
Member

@JavierSegoviaCordoba what do you mean default requesters?

@JavierSegoviaCordoba
Copy link
Member

PRs can be merged without approvals, maybe it is intended tho

@nomisRev
Copy link
Member

Yes, I actually think it would be easier if we automatically merge if the PR is green. I was hesitant of this in the beginning, but now I am wondering why not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants