Skip to content

Conversation

@v1v
Copy link
Member

@v1v v1v commented Jun 16, 2025

What does this PR do?

Support all the active branches when running the gH action for bumping versions using updatecli

Why is it important?

Because the backports have been merged:

Checklist

  • I have read and understood the pull request guidelines of this project.
  • 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/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

otherwise there are errors without failing in updatecli
sourceid: lastStableStackSnapshot
spec:
automerge: true
automerge: false
Copy link
Member Author

Choose a reason for hiding this comment

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

We cannot use automerge here, the branch protections have a higher precedence and the GitHub Actions [bot] does not support it yet, see https://github.com/orgs/community/discussions/13836.

Pull Request available at:

	https://github.com/elastic/elastic-agent/pull/8576

ERROR: action stage:	"Merge method merge commits are not allowed on this repository and Pull request User is not authorized for this protected branch"
Existing GitHub pull request found: https://github.com/elastic/elastic-agent/pull/8576
ERROR: running actions:
errors occurred while running actions:
	* Merge method merge commits are not allowed on this repository and Pull request User is not authorized for this protected branch

=============================

@v1v v1v marked this pull request as ready for review June 18, 2025 07:58
@v1v v1v requested review from a team as code owners June 18, 2025 07:58
@pazone
Copy link
Contributor

pazone commented Jun 30, 2025

First we need to merge these backports: #8540

@v1v v1v closed this Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants