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

chore(deps): update trinodb/trino docker tag to v448 #9205

Merged
merged 1 commit into from
May 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 17, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
trinodb/trino major 447 -> 448

Configuration

πŸ“… Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

β™» 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, check this box

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

@renovate renovate bot added dependencies Issues or PRs related to dependencies trino The Trino backend labels May 17, 2024
@renovate renovate bot force-pushed the renovate/trinodb-trino-448.x branch from 19b1b17 to 9fe6c94 Compare May 17, 2024 12:58
@renovate renovate bot force-pushed the renovate/trinodb-trino-448.x branch from 9fe6c94 to 0b31d77 Compare May 17, 2024 14:24
@cpcloud cpcloud added this to the 9.1 milestone May 18, 2024
@cpcloud cpcloud enabled auto-merge (squash) May 18, 2024 13:36
@cpcloud cpcloud merged commit b18abca into main May 18, 2024
82 checks passed
@cpcloud cpcloud deleted the renovate/trinodb-trino-448.x branch May 18, 2024 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Issues or PRs related to dependencies trino The Trino backend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant