elastic / data-extraction-service

Other
12 stars 0 forks source link

Update openresty/openresty Docker tag to v1.25.3.2 #40

Open elastic-renovate-prod[bot] opened 1 month ago

elastic-renovate-prod[bot] commented 1 month ago

This PR contains the following updates:

Package Type Update Change
openresty/openresty minor 1.21.4.1-0-alpine -> 1.25.3.2-0-alpine
openresty/openresty final minor 1.21.4.1-0-alpine -> 1.25.3.2-0-alpine

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.



This PR has been generated by Renovate Bot.

artem-shelkovnikov commented 1 month ago

@elastic/ingestion-team are we confident that we can merge such changes with just CI checks?

navarone-feekery commented 1 month ago

@artem-shelkovnikov no I would prefer we test this change manually. I can look at it later. Do you know what the urgency is on merging this?

artem-shelkovnikov commented 1 month ago

Not sure about urgency - might be worth to ask the Renovate internal team about it.

It's something new that's touching all our repos, so not everything is clear to me.

seanstory commented 1 month ago

Renovate is optional. I enabled it for this repo, but we can revisit that decision if it was hasty. For example, I chose to not enable it for Thumbnails4j, since we don't really have the bandwidth to do the manual testing on that repo. If we don't have high confidence in this repo's CI right now either, then renovate might be more hassle than help.

This is not the same as Snyk, where these update suggestions are necessarily security related, AFAIU. The goal is to just help keep dependencies up-to-date.