Kiran Godishala

@vsubrama001 @codemedow - Have you tried 1.26.7? Can you confirm if you are seeing the issue with 1.26.7?

@sanopsmx - it seems there are conflicts. Could you resolve them first?

@idiamant - There was one fix already provided. Error codes 429, 503 were made retry-able. Can you give more details like which spinnaker version are you using? Do you see...

@nvoxland @dbyron-sf - I am willing to work on this change. Is there any developer guide sort of documentation to start with?

@nvoxland - initially I thought of going with creating a new interface(say ChangeVisitor) similar to SqlVisitor to apply modifyChange but then I though the complete logic can be implemented under...

Thanks for the response @nvoxland. I took off on Friday. Will try to implement the changes as suggested above and add comments here if I need any more inputs.

> If it's in the root, it acts like preconditions and gets "hoisted" across all the include'd changesets, not just to the particular changelog it's in. @nvoxland - you mean...

@nvoxland - created PR - https://github.com/liquibase/liquibase/pull/3978 I took a design decision to apply the `ChangeVisitor` while loading the change itself. Please review and provide feedback.

Cloudrun support is added to spinnaker. More details can be found here: https://github.com/spinnaker/governance/issues/302

We are facing similar issue - https://github.com/spinnaker/spinnaker/issues/6941 We upgraded liquibase from 3.10.3 to 4.24.0 in Spinnaker and started seeing errors like this - `8:f0bfebd55de9168e38a8ef9c7217c610 but is now: 8:d41d8cd98f00b204e9800998ecf8427e`. Manual overwriting...