[AUTO] Incremented version to 1.2.5.

[github-actions]

I've noticed that a new tag 1.2.4.0 was pushed, and incremented the version from 1.2.4 to 1.2.5.

[dblock]

CI didn't get kicked here :(

[dblock]

@VachaShah Do you know how to make CI trigger on this? Do we need a PAT? How do I set this up?

[VachaShah]

@VachaShah Do you know how to make CI trigger on this? Do we need a PAT? How do I set this up?

PAT can definitely work but it would be only for a single repo. I am currently working on a Github App to solve this for other such cases (dependabot and backport). We could use the same token here as well and across other repos.

[dblock]

@VachaShah Do you know how to make CI trigger on this? Do we need a PAT? How do I set this up?

PAT can definitely work but it would be only for a single repo. I am currently working on a Github App to solve this for other such cases (dependabot and backport). We could use the same token here as well and across other repos.

I'd rather wait for this. Thanks.

[VachaShah]

@VachaShah Do you know how to make CI trigger on this? Do we need a PAT? How do I set this up?

PAT can definitely work but it would be only for a single repo. I am currently working on a Github App to solve this for other such cases (dependabot and backport). We could use the same token here as well and across other repos.

I'd rather wait for this. Thanks.

@dblock We can now use the Github App opensearch-trigger-bot token to trigger CIs on this.

[dblock]

@VachaShah Do you know how to make CI trigger on this? Do we need a PAT? How do I set this up?

PAT can definitely work but it would be only for a single repo. I am currently working on a Github App to solve this for other such cases (dependabot and backport). We could use the same token here as well and across other repos.

I'd rather wait for this. Thanks.

@dblock We can now use the Github App opensearch-trigger-bot token to trigger CIs on this.

Don't hold back updating the auto-increment version workflows :)