Skip to content
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

Bump elastic-agent-lib version to 0.17.3 #41637

Merged
merged 4 commits into from
Nov 14, 2024

Conversation

khushijain21
Copy link
Contributor

Proposed commit message

Bump elastic-agent-lib version to 0.17.3 and add updates the change of behaviour in changelog

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

@khushijain21 khushijain21 requested a review from a team as a code owner November 14, 2024 06:01
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 14, 2024
@khushijain21 khushijain21 changed the title Bump elastic-agent-lib version to 0.17.3 and Changelog Bump elastic-agent-lib version to 0.17.3 Nov 14, 2024
@khushijain21 khushijain21 requested a review from rdner November 14, 2024 06:01
@khushijain21 khushijain21 added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Nov 14, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 14, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

Copy link
Contributor

mergify bot commented Nov 14, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @khushijain21? 🙏.
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

Copy link
Contributor

mergify bot commented Nov 14, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Nov 14, 2024
CHANGELOG.next.asciidoc Outdated Show resolved Hide resolved
@khushijain21 khushijain21 requested a review from rdner November 14, 2024 13:24
@khushijain21 khushijain21 enabled auto-merge (squash) November 14, 2024 13:29
@AndersonQ
Copy link
Member

FYI: I'm updating 8.16 to elastic-agent-libs 0.17.3 here.

@rdner
Copy link
Member

rdner commented Nov 14, 2024

@AndersonQ that we need to put the same changelog entry there. I'd rather backport this PR to 8.16.

@khushijain21 khushijain21 merged commit 3e9ab52 into elastic:main Nov 14, 2024
142 checks passed
mergify bot pushed a commit that referenced this pull request Nov 14, 2024
* Bump elastic-agent-lib version and Changelog

---------

Co-authored-by: Denis <[email protected]>
(cherry picked from commit 3e9ab52)
rdner pushed a commit that referenced this pull request Nov 14, 2024
* Bump elastic-agent-lib version and Changelog

---------

Co-authored-by: Denis <[email protected]>
(cherry picked from commit 3e9ab52)

Co-authored-by: Khushi Jain <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants