github-actions(updatecli): use oblt-actions, pin version and avoid diverging PRs

[v1v]

Proposed commit message

• Use https://github.com/elastic/oblt-actions/tree/main/updatecli/run-and-notify#updateclirun-and-notify
• Use .tool-versions
• Use force: false, see See Running parallel pipelines with different parameters some are skipped updatecli/updatecli#2211 (comment)
• Update mergify rules to delete the branches

This should avoid issues when the changes diverge and then PRs are closed:

• https://github.com/elastic/beats/pulls?q=sort%3Aupdated-desc+is%3Apr+author%3Aapp%2Fgithub-actions+is%3Aopen

Therefore, it will not update those PRs but keep the ones that are open.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Updatecli

I deleted the branch for #43744 then I ran:

GITHUB_TOKEN=$(gh auth token) \
  GITHUB_ACTOR=v1v \
  BRANCH=8.x \
  updatecli --experimental apply \
    --config .github/workflows/updatecli.d/bump-elastic-stack-snapshot.yml \
    --values .github/workflows/updatecli.d/values.d/scm.yml

CI

See

• https://github.com/elastic/beats/actions/runs/14312238120
• https://github.com/elastic/beats/actions/runs/14312240864
• https://github.com/elastic/beats/actions/runs/14312297750

Related issues

Use cases

Screenshots

Logs

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @v1v? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[v1v]

We maintain elastic/oblt-actions so we can avoid the burden of bumping versions

[v1v]

elastic/oblt-actions/updatecli/run-and-notify does the notification if any failures, DRY

[v1v]

default to main, but let's avoid being hardcoded here, so we can use the config file locally

[v1v]

I'll create a follow-up to bump this version as we do in some other places

[AndersonQ]

Is this what would prevent the force-push that closes the PR?

[v1v]

Correct, that's the alternative, already added to the description, but see this link:

• Running parallel pipelines with different parameters some are skipped updatecli/updatecli#2211 (comment)

This solves the problem partially, as it will not create any new updates with a new version either updating the existing open PR or creating a new of if an existing open PR exists.

I need to see if using an old version of updatecli, as mentioned at updatecli/updatecli#2211 (comment), reverts to the original approach (see https://github.com/elastic/beats/pull/41241/commits).

[ev1yehor]

LGTM

[AndersonQ]

Looks good, I'll wait the conflicts to be fixed then I'll approve the PR

[v1v]

@AndersonQ , this is now ready 🙏