Skip to content

Update shedlock monorepo to v6.4.0 #41

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 7, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
net.javacrumbs.shedlock:shedlock-provider-jdbc-template (source) 6.3.0 -> 6.4.0 age adoption passing confidence
net.javacrumbs.shedlock:shedlock-spring (source) 6.3.0 -> 6.4.0 age adoption passing confidence

Release Notes

lukas-krecan/ShedLock (net.javacrumbs.shedlock:shedlock-provider-jdbc-template)

v6.4.0

  • Support ElasticSearch 9
  • Dependency updates

v6.3.1

  • Add shedlock-provider-jdbc to bom (thanks @​svenallers)
  • Dependency updates

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/shedlock-monorepo branch from 2e7b168 to 853c53b Compare April 19, 2025 19:03
@renovate renovate bot changed the title Update shedlock monorepo to v6.3.1 Update shedlock monorepo to v6.4.0 Apr 19, 2025
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.

0 participants