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 groovy monorepo to v4.0.21 #789

Merged
merged 1 commit into from Apr 9, 2024
Merged

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 9, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.apache.groovy:groovy-xml (source) 4.0.20 -> 4.0.21 age adoption passing confidence
org.apache.groovy:groovy-nio (source) 4.0.20 -> 4.0.21 age adoption passing confidence
org.apache.groovy:groovy-json (source) 4.0.20 -> 4.0.21 age adoption passing confidence
org.apache.groovy:groovy (source) 4.0.20 -> 4.0.21 age adoption passing confidence
org.apache.groovy:groovy-bom (source) 4.0.20 -> 4.0.21 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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 these updates again.


  • If you want to rebase/retry this PR, check this box

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

@hazendaz hazendaz self-assigned this Apr 9, 2024
@hazendaz hazendaz merged commit 59141d8 into master Apr 9, 2024
34 checks passed
@renovate renovate bot deleted the renovate/groovy-monorepo branch April 9, 2024 14:32
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.

None yet

1 participant