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

fix(deps): update groovy monorepo to v3.0.20 #1731

Merged
merged 1 commit into from
Feb 27, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 31, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.codehaus.groovy:groovy-json (source) 3.0.11 -> 3.0.20 age adoption passing confidence
org.codehaus.groovy:groovy-templates (source) 3.0.11 -> 3.0.20 age adoption passing confidence
org.codehaus.groovy:groovy-xml (source) 3.0.11 -> 3.0.20 age adoption passing confidence
org.codehaus.groovy:groovy-dateutil (source) 3.0.11 -> 3.0.20 age adoption passing confidence
org.codehaus.groovy:groovy (source) 3.0.11 -> 3.0.20 age adoption passing confidence

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.

@renovate renovate bot added the type: dependency upgrade Pull requests that update a dependency file label Mar 31, 2023
@CLAassistant
Copy link

CLAassistant commented Mar 31, 2023

CLA assistant check
All committers have signed the CLA.

@renovate renovate bot force-pushed the renovate/groovy-monorepo branch from e00ba5f to 57e601c Compare March 31, 2023 11:34
@renovate renovate bot changed the title Update groovy monorepo Update groovy monorepo to v3.0.17 Mar 31, 2023
@renovate renovate bot force-pushed the renovate/groovy-monorepo branch from 57e601c to dea0b45 Compare June 29, 2023 15:26
@renovate renovate bot changed the title Update groovy monorepo to v3.0.17 Update groovy monorepo Jun 29, 2023
@renovate renovate bot force-pushed the renovate/groovy-monorepo branch from dea0b45 to 42150f8 Compare June 29, 2023 20:05
@renovate renovate bot changed the title Update groovy monorepo Update groovy monorepo to v3.0.18 Jun 29, 2023
@renovate renovate bot force-pushed the renovate/groovy-monorepo branch from 42150f8 to ff9f52a Compare July 6, 2023 11:17
@renovate renovate bot force-pushed the renovate/groovy-monorepo branch from ff9f52a to 62b4c5a Compare August 22, 2023 08:49
@renovate renovate bot changed the title Update groovy monorepo to v3.0.18 Update groovy monorepo Aug 22, 2023
@renovate renovate bot changed the title Update groovy monorepo Update groovy monorepo to v3.0.19 Aug 22, 2023
@renovate renovate bot changed the title Update groovy monorepo to v3.0.19 Update groovy monorepo Dec 22, 2023
@renovate renovate bot changed the title Update groovy monorepo Update groovy monorepo to v3.0.20 Dec 22, 2023
@renovate renovate bot force-pushed the renovate/groovy-monorepo branch 2 times, most recently from 5c49519 to f9bf85e Compare January 10, 2024 13:56
@puneetbehl
Copy link
Contributor

@matrei Can. you please take a look at it?

@renovate renovate bot changed the base branch from 8.0.x to 8.1.x February 2, 2024 07:01
@puneetbehl puneetbehl merged commit fe26ba8 into 8.1.x Feb 27, 2024
7 checks passed
@renovate renovate bot changed the title Update groovy monorepo to v3.0.20 fix(deps): update groovy monorepo to v3.0.20 Feb 27, 2024
@renovate renovate bot deleted the renovate/groovy-monorepo branch February 27, 2024 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: dependency upgrade Pull requests that update a dependency file type: minor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants