Skip to content

Conversation

@pierrehilbert
Copy link
Contributor

What does this PR do?

Why is it important?

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?
  • ...

@pierrehilbert pierrehilbert requested a review from a team as a code owner December 8, 2025 12:30
@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Dec 8, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@mergify
Copy link
Contributor

mergify bot commented Dec 8, 2025

This pull request does not have a backport label. Could you fix it @pierrehilbert? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports 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.

@ycombinator
Copy link
Contributor

Hi @pierrehilbert, could you please add a CHANGELOG fragment for this PR? Thanks.

@cmacknz
Copy link
Member

cmacknz commented Dec 9, 2025

We aren't ready to tell external users about windows/arm support so I am fine with no changelog on this one.

@pierrehilbert
Copy link
Contributor Author

The goal here is to make incremental progress and to be able to run integration tests with Windows ARM.
Once everything will be green, we will add a changelog to make it clear to our users.
If we are adding the changelog in this PR, we are taking the risk to have it publish in our next release even if we are not able to support it.

@elasticmachine
Copy link
Contributor

elasticmachine commented Dec 10, 2025

💔 Build Failed

Failed CI Steps

History

cc @pierrehilbert

@pierrehilbert pierrehilbert merged commit 1e98fe8 into main Dec 12, 2025
22 checks passed
@pierrehilbert pierrehilbert deleted the windows-arm64-artifact branch December 12, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants