squakez commented on issue #5986: URL: https://github.com/apache/camel-k/issues/5986#issuecomment-3839733942
That's correct. We probably need to identify the different places where the variable is used and change it statically. I think that having the dependabot managing an upgrade may be complicated because the dependency is scattered around the code and scripts. Great idea to update the `Makefile`. We alreay have a `make generate` (which it also happen on autogen at night time) where you can just include the new SHA mapping script. Right now we are controlling that value via a variable in https://github.com/apache/camel-k/blob/60925a32d1dbea892e1e50c8089e3b9e55835ecb/script/Makefile#L53C36-L53C54 We should introduce a new variable containing such a SHA. With this new variable we only control the Integration base image. This variable is the one which we can change via this new script, only changing the value in the Makefile in https://github.com/apache/camel-k/blob/60925a32d1dbea892e1e50c8089e3b9e55835ecb/script/Makefile#L191. About the documentation, you can just change the format and include a bogus value. I don't see any value in doing the update there, as the user have to look and change it anyway. Feel free to ping me or just open a draft PR to include any further detail, but I think the plan is quite good. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
