Skip to content

deps: use the latest updatecli version #45484

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 22, 2025
Merged

Conversation

v1v
Copy link
Member

@v1v v1v commented Jul 21, 2025

Proposed commit message

Bump updatecli version to the latest available, so the latest updatecli policies work out of the box.

#45478 was merged but introduced a hard dependency with the updatecli version, see https://github.com/updatecli/policies/blob/main/updatecli/policies/autodiscovery/updatecli/CHANGELOG.md#090

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

In the CI only, see the below runs:

Related issues

Use cases

Screenshots

Logs

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 21, 2025
@botelastic
Copy link

botelastic bot commented Jul 21, 2025

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

Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify mergify bot assigned v1v Jul 21, 2025
Copy link
Contributor

mergify bot commented Jul 21, 2025

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 v1v requested review from a team July 21, 2025 06:45
@v1v v1v marked this pull request as ready for review July 21, 2025 06:45
@v1v v1v requested a review from a team as a code owner July 21, 2025 06:45
@v1v v1v requested review from leehinman and andrzej-stencel July 21, 2025 06:45
Copy link

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@v1v v1v enabled auto-merge (squash) July 21, 2025 15:28
@v1v v1v merged commit 4a24152 into main Jul 22, 2025
26 checks passed
@v1v v1v deleted the feature/bump-version-updatecli1 branch July 22, 2025 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants