Skip to content

Change stack version requirements due to the breaking changes #15268

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.

Sign up for GitHub

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 2 commits into from
Sep 10, 2025
Merged

Change stack version requirements due to the breaking changes #15268

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8c5a110
Change stack version requirements due to the breaking changes
rdner Sep 10, 2025
7f0c9f7
Use a minor version instead of patch
rdner Sep 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion packages/elastic_agent/changelog.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,13 @@
# newer versions go on top

- version: "2.5.3"
changes:
- description: Update version requirements due to the breaking change in metric names
type: enhancement
link: "https://github.com/elastic/integrations/pull/15268"
Copy link
Member

@jsoriano jsoriano Sep 10, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

I would suggest to release this as 2.6.0.

Suggested change
- version: "2.5.3"
changes:
- description: Update version requirements due to the breaking change in metric names
type: enhancement
link: "https://github.com/elastic/integrations/pull/15268"
- version: "2.6.0"
changes:
- description: Update version requirements due to the breaking change in metric names
type: enhancement
link: "https://github.com/elastic/integrations/pull/15268"

After releasing 2.6.0, create a backport branch from 2.5.2, revert the breaking change in this branch, and release a 2.5.3 version from there.

This way stacks >= 8.15.0 will use 2.6.0, and older versions will use the fixed 2.5.3.

Copy link
Member Author

@rdner rdner Sep 10, 2025

Choose a reason for hiding this comment

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

@jsoriano would it make upgrading to the "broken" 2.5.2 impossible?

Copy link
Member Author

@rdner rdner Sep 10, 2025

Choose a reason for hiding this comment

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

As discussed, we release 2.6.0 and 2.5.3 backport first. Then we remove the "broken" 2.5.2 from the registry.

Copy link
Member Author

@rdner rdner Sep 10, 2025

Choose a reason for hiding this comment

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

The 2.5 backport PR #15273

- version: "2.5.2"
changes:
- description: Update `queue.filled.pct.events` to `queue.filled.pct` metric name
- description: Update `queue.filled.pct.events` to `queue.filled.pct` metric name
type: enhancement
link: "https://github.com/elastic/integrations/pull/15244"
- version: "2.5.1"
Expand Down
4 changes: 2 additions & 2 deletions packages/elastic_agent/manifest.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
name: elastic_agent
title: Elastic Agent
version: 2.5.2
version: 2.5.3
description: Collect logs and metrics from Elastic Agents.
type: integration
format_version: 3.1.4
categories: ["elastic_stack"]
conditions:
kibana:
version: "^8.11.2 || ^9.0.0"
version: "^8.15.0 || ^9.0.0"
elastic:
subscription: basic
owner:
Expand Down