diff --git a/changelog/8.19.14.asciidoc b/changelog/8.19.14.asciidoc new file mode 100644 index 00000000000..2025c77e1ec --- /dev/null +++ b/changelog/8.19.14.asciidoc @@ -0,0 +1,54 @@ +// begin 8.19.14 relnotes + +[[release-notes-8.19.14]] +== 8.19.14 + +Review important information about the 8.19.14 release. + + + + + + + + + +[discrete] +[[new-features-8.19.14]] +=== New features + +The 8.19.14 release adds the following new and notable features. + + + + +* Add Cloud Defend Integration support to the helm chart. https://github.com/elastic/elastic-agent/pull/13074[#13074] + + +[discrete] +[[enhancements-8.19.14]] +=== Enhancements + + + + +* Update Go to v1.25.8. https://github.com/elastic/elastic-agent/pull/10156[#10156] +* Update OTel components to v0.145.0. https://github.com/elastic/elastic-agent/pull/13104[#13104] +* Update OTel to v1.54.0/v0.148.0. https://github.com/elastic/elastic-agent/pull/13317[#13317] + + + + +[discrete] +[[bug-fixes-8.19.14]] +=== Bug fixes + + + + +* Update Kubernetes example manifests and add `HOSTFS_PROC_PATH` environment variable due to `procfs` fix in `cloud-defend` as well as mount points required for `cloud-defend`. https://github.com/elastic/elastic-agent/pull/12989[#12989] +* Fix an issue where some components could be missing from the status output. https://github.com/elastic/elastic-agent/pull/13119[#13119] +* Prevent zombie processes when component fails to shutdown. https://github.com/elastic/elastic-agent/pull/13188[#13188] https://github.com/elastic/elastic-agent/issues/13272[#13272] +* Fix container enrollment so it does not re-enroll when the Fleet URL is the same. https://github.com/elastic/elastic-agent/pull/13187[#13187] + +// end 8.19.14 relnotes diff --git a/changelog/8.19.14.yaml b/changelog/8.19.14.yaml new file mode 100644 index 00000000000..06e59adc1b3 --- /dev/null +++ b/changelog/8.19.14.yaml @@ -0,0 +1,136 @@ +version: 8.19.14 +entries: + - kind: enhancement + summary: Update Go version to 1.25.8 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/10156 + issue: [] + impact: "" + action: "" + timestamp: 1758822287 + file: + name: 1758822287-bump-golang-1.25.8.yaml + checksum: fa096c55691ea42f62d54f8187450a0c8cdd5a7b + - kind: bug-fix + summary: | + Updated k8s example manifests. Added HOSTFS_PROC_PATH environment variable due-to procfs fix in cloud-defend + and mount points required for cloud-defend. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/12989 + issue: [] + impact: "" + action: "" + timestamp: 1772715054 + file: + name: 1772715054-cloud-defend-procfs.yaml + checksum: 380617ec2ad2b4eb8e982c733e2a02e9005e46ac + - kind: feature + summary: Add Cloud Defend Integration support to the helm chart + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13074 + issue: [] + impact: "" + action: "" + timestamp: 1772815729 + file: + name: 1772815729-cloud-defend-helm-chart.yaml + checksum: 46069879efe82be441003d51ef5110ebfeb1124d + - kind: enhancement + summary: Update OTel components to v0.145.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13104 + issue: [] + impact: "" + action: "" + timestamp: 1773138205 + file: + name: 1773138205-update-otel-components-to-v0.145.0.yaml + checksum: f7d0ca59efef03c3ed09b04422cdf6be24f012c1 + - kind: bug-fix + summary: Fix an issue where some components could be missing from the status output + description: | + In some cases, a late update from an older component instance could overwrite a newer state. This could cause components to be missing from the status output. With this fix, updates from older instances are ignored if a newer update has already been processed. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13119 + issue: [] + impact: "" + action: "" + timestamp: 1773217838 + file: + name: 1773217838-main.yaml + checksum: 9ff6f8a3221e3ae28562f165dbd9d4bad684d7d3 + - kind: unknown + summary: Fix the elastic-agent build time as reported by the version command + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13140 + issue: [] + impact: "" + action: "" + timestamp: 1773392178 + file: + name: 1773392178-fix-agent-buildtime.yaml + checksum: 570441a6912ee2ad229ca16be43edd6d8a47bf76 + - kind: bug-fix + summary: Prevent zombie processes when component fails to shutdown + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13188 + issue: + - https://github.com/elastic/elastic-agent/issues/13272 + impact: "" + action: "" + timestamp: 1773697016 + file: + name: 1773697016-Prevent-zombie-processes-when-component-fails-to-shutdown.yaml + checksum: f175d8dd952507f35c2f8d49f3c14fff9bdfd846 + - kind: bug-fix + summary: fix container enrollment to not re-enroll when the fleet_url is the same + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13187 + issue: [] + impact: "" + action: "" + timestamp: 1773760327 + file: + name: 1773760327-fix-container-enrollment-to-not-re-enroll-when-the-fleet_url-is-the-same.yaml + checksum: 364abe82a2729e67dc33b89b6f4177eedaa4fac7 + - kind: enhancement + summary: update otel to v1.54.0/v0.148.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13317 + issue: [] + impact: "" + action: "" + timestamp: 1774382936 + file: + name: 1774382936-update-otel-to-v1.54.0-v0.148.0.yaml + checksum: 3e109ffc27e1ee86ca926de3a574c5e6c5cb275a + - kind: other + summary: upgrade nodejs to v22.22.2 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/13391 + issue: [] + impact: "" + action: "" + timestamp: 1774970286 + file: + name: 1774970286-dependency-upgrade-nodejs-v22.22.2.yaml + checksum: 4d04aad7a92b42313addfed47353d2d87984b772 diff --git a/changelog/fragments/1758822287-bump-golang-1.25.8.yaml b/changelog/fragments/1758822287-bump-golang-1.25.8.yaml deleted file mode 100644 index 0137e55863e..00000000000 --- a/changelog/fragments/1758822287-bump-golang-1.25.8.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Update Go version to 1.25.8 - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/10156 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1772715054-cloud-defend-procfs.yaml b/changelog/fragments/1772715054-cloud-defend-procfs.yaml deleted file mode 100644 index adf0959819a..00000000000 --- a/changelog/fragments/1772715054-cloud-defend-procfs.yaml +++ /dev/null @@ -1,47 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: | - Updated k8s example manifests. Added HOSTFS_PROC_PATH environment variable due-to procfs fix in cloud-defend - and mount points required for cloud-defend. - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/12989 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1772815729-cloud-defend-helm-chart.yaml b/changelog/fragments/1772815729-cloud-defend-helm-chart.yaml deleted file mode 100644 index b841a187c48..00000000000 --- a/changelog/fragments/1772815729-cloud-defend-helm-chart.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Add Cloud Defend Integration support to the helm chart - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: "elastic-agent" - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/13074 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1773138205-update-otel-components-to-v0.145.0.yaml b/changelog/fragments/1773138205-update-otel-components-to-v0.145.0.yaml deleted file mode 100644 index e6c301697ce..00000000000 --- a/changelog/fragments/1773138205-update-otel-components-to-v0.145.0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Update OTel components to v0.145.0 - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1773217838-main.yaml b/changelog/fragments/1773217838-main.yaml deleted file mode 100644 index 7adc2cf96eb..00000000000 --- a/changelog/fragments/1773217838-main.yaml +++ /dev/null @@ -1,48 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Fix an issue where some components could be missing from the status output - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: > - In some cases, a late update from an older component instance could overwrite a newer state. - This could cause components to be missing from the status output. - With this fix, updates from older instances are ignored if a newer update has already been processed. - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1773392178-fix-agent-buildtime.yaml b/changelog/fragments/1773392178-fix-agent-buildtime.yaml deleted file mode 100644 index 9c62aa677ac..00000000000 --- a/changelog/fragments/1773392178-fix-agent-buildtime.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug_fix - -# Change summary; a 80ish characters long description of the change. -summary: Fix the elastic-agent build time as reported by the version command - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1773697016-Prevent-zombie-processes-when-component-fails-to-shutdown.yaml b/changelog/fragments/1773697016-Prevent-zombie-processes-when-component-fails-to-shutdown.yaml deleted file mode 100644 index 8ab5754109e..00000000000 --- a/changelog/fragments/1773697016-Prevent-zombie-processes-when-component-fails-to-shutdown.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Prevent zombie processes when component fails to shutdown - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: | - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/13272 diff --git a/changelog/fragments/1773760327-fix-container-enrollment-to-not-re-enroll-when-the-fleet_url-is-the-same.yaml b/changelog/fragments/1773760327-fix-container-enrollment-to-not-re-enroll-when-the-fleet_url-is-the-same.yaml deleted file mode 100644 index 97436bafb2f..00000000000 --- a/changelog/fragments/1773760327-fix-container-enrollment-to-not-re-enroll-when-the-fleet_url-is-the-same.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: fix container enrollment to not re-enroll when the fleet_url is the same - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1773838908-update-otel-components-to-v0.147.0.yaml b/changelog/fragments/1773838908-update-otel-components-to-v0.147.0.yaml deleted file mode 100644 index 2eb97b44e20..00000000000 --- a/changelog/fragments/1773838908-update-otel-components-to-v0.147.0.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Update OTel components to v0.147.0 - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1774382936-update-otel-to-v1.54.0-v0.148.0.yaml b/changelog/fragments/1774382936-update-otel-to-v1.54.0-v0.148.0.yaml deleted file mode 100644 index f7d72e513ad..00000000000 --- a/changelog/fragments/1774382936-update-otel-to-v1.54.0-v0.148.0.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: update otel to v1.54.0/v0.148.0 - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1774970286-dependency-upgrade-nodejs-v22.22.2.yaml b/changelog/fragments/1774970286-dependency-upgrade-nodejs-v22.22.2.yaml deleted file mode 100644 index 557a5cf2c23..00000000000 --- a/changelog/fragments/1774970286-dependency-upgrade-nodejs-v22.22.2.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: other - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: upgrade nodejs to v22.22.2 - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234