diff --git a/changelog/9.1.3.asciidoc b/changelog/9.1.3.asciidoc new file mode 100644 index 00000000000..9652f191349 --- /dev/null +++ b/changelog/9.1.3.asciidoc @@ -0,0 +1,54 @@ +// begin 9.1.3 relnotes + +[[release-notes-9.1.3]] +== 9.1.3 + +Review important information about the 9.1.3 release. + +[discrete] +[[security-updates-9.1.3]] +=== Security updates + + +elastic-agent:: + +* Upgrade To Go to version 1.24.6. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9287[#https://github.com/elastic/elastic-agent/pull/9287] + + +[discrete] +[[new-features-9.1.3]] +=== New features + +The 9.1.3 release adds the following new and notable features. + + +* Adjust The Timeout For Elastic Defend Check Command. {-pull}https://github.com/elastic/elastic-agent/pull/9213[#https://github.com/elastic/elastic-agent/pull/9213] + + +[discrete] +[[enhancements-9.1.3]] +=== Enhancements + + +elastic-agent:: + +* Update Otel Components To V0.130.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9329[#https://github.com/elastic/elastic-agent/pull/9329] + + + + +[discrete] +[[bug-fixes-9.1.3]] +=== Bug fixes + + +elastic-agent:: + +* On Windows, Retry Saving The Agent Information File To Disk. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9224[#https://github.com/elastic/elastic-agent/pull/9224] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5862[#https://github.com/elastic/elastic-agent/issues/5862] +* Correct Hints Annotations Parsing To Resolve Only `${Kubernetes.*}` Placeholders Instead Of Resolving All `${...}` Patterns. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9307[#https://github.com/elastic/elastic-agent/pull/9307] +* Treat Exit Code 28 From Endpoint Binary As Non-Fatal. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9320[#https://github.com/elastic/elastic-agent/pull/9320] +* Fixed Jitter Backoff Strategy Reset. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9342[#https://github.com/elastic/elastic-agent/pull/9342] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/8864[#https://github.com/elastic/elastic-agent/issues/8864] +* Fix Docker Container Failing To Start With No Matching Vars: ${Env.elasticsearch_api_key:} And Similar Errors By Restoring Support For `:` To Set Default Values. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9451[#https://github.com/elastic/elastic-agent/pull/9451] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/9328[#https://github.com/elastic/elastic-agent/issues/9328] +* Fix Deb Upgrade By Stopping Elastic-Agent Service Before Stopping Endpoint. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/9462[#https://github.com/elastic/elastic-agent/pull/9462] + +// end 9.1.3 relnotes diff --git a/changelog/9.1.3.yaml b/changelog/9.1.3.yaml new file mode 100644 index 00000000000..520175dd45a --- /dev/null +++ b/changelog/9.1.3.yaml @@ -0,0 +1,105 @@ +version: 9.1.3 +entries: + - kind: feature + summary: Adjust the timeout for Elastic Defend check command + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/9213 + issue: [] + timestamp: 1753950420 + file: + name: 1753950420-adjust-endpoint-check-timeout.yaml + checksum: 8128c245da5eef165a531e45f95e3f964bbd1817 + - kind: bug-fix + summary: On Windows, retry saving the Agent information file to disk + description: | + Saving the Agent information file involves renaming/moving a file to its final destination. However, on Windows, it is sometimes not possible to rename/move a file to its destination file because the destination file is locked by another process (e.g. antivirus software). For such situations, we now retry the save operation on Windows. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9224 + issue: + - https://github.com/elastic/elastic-agent/issues/5862 + timestamp: 1754346816 + file: + name: 1754346816-fleet-enc-save-retries.yaml + checksum: fab4b29d2404c210dcb1441eb88e84dd3f6c9ad1 + - kind: bug-fix + summary: Correct hints annotations parsing to resolve only `${kubernetes.*}` placeholders instead of resolving all `${...}` patterns. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9307 + issue: [] + timestamp: 1754944400 + file: + name: 1754944400-k8s-hints-env-vars-in-annotations.yaml + checksum: 55ccb4d795ad7556a9c8ecad5bd33a0a0893042b + - kind: bug-fix + summary: Treat exit code 28 from Endpoint binary as non-fatal + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9320 + issue: [] + timestamp: 1755059673 + file: + name: 1755059673-endpoint-28-not-fatal.yaml + checksum: d8fc4bbea824309297a7dcf508fd99fb62e86877 + - kind: bug-fix + summary: Fixed jitter backoff strategy reset + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9342 + issue: + - https://github.com/elastic/elastic-agent/issues/8864 + timestamp: 1755076749 + file: + name: 1755076749-fix-jitter-backoff-strategy-reset.yaml + checksum: 1969a9a0221227c476f94e27a4ef3946b3853416 + - kind: enhancement + summary: Update OTel components to v0.130.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9329 + issue: [] + timestamp: 1755149089 + file: + name: 1755149089-update-otel-components-to-v0.130.0.yaml + checksum: b3e16c76d7df9bc7724df86777bcc67bc88f8691 + - kind: bug-fix + summary: 'Fix Docker container failing to start with no matching vars: ${env.ELASTICSEARCH_API_KEY:} and similar errors by restoring support for `:` to set default values.' + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9451 + issue: + - https://github.com/elastic/elastic-agent/issues/9328 + timestamp: 1755544412 + file: + name: 1755544412-Fix-default-constant-support-in-output-configuration.yaml + checksum: 9b389ac54a3b8a7aaec24da9223bff8a306c4d8b + - kind: security + summary: Upgrade to Go 1.24.6. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9287 + issue: [] + timestamp: 1755547590 + file: + name: 1755547590-Upgrade-to-Go-1.24.6..yaml + checksum: e2f37c3bfe8bda55a0ec6c32cf604e44dc4f5d43 + - kind: bug-fix + summary: Fix deb upgrade by stopping elastic-agent service before stopping endpoint + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9462 + issue: [] + timestamp: 1755601979 + file: + name: 1755601979-deb-upgrade-stop-agent-service.yaml + checksum: fff4e813c33f7eccb8ebf9a49698781df5734b79 diff --git a/changelog/fragments/1753950420-adjust-endpoint-check-timeout.yaml b/changelog/fragments/1753950420-adjust-endpoint-check-timeout.yaml deleted file mode 100644 index 2a4bcef3ac9..00000000000 --- a/changelog/fragments/1753950420-adjust-endpoint-check-timeout.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: feature - -# Change summary; a 80ish characters long description of the change. -summary: Adjust the timeout for Elastic Defend check 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: - -# 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/1754346816-fleet-enc-save-retries.yaml b/changelog/fragments/1754346816-fleet-enc-save-retries.yaml deleted file mode 100644 index e5cbb87b5b9..00000000000 --- a/changelog/fragments/1754346816-fleet-enc-save-retries.yaml +++ /dev/null @@ -1,36 +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: On Windows, retry saving the Agent information file to disk - -# 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: > - Saving the Agent information file involves renaming/moving a file to its final - destination. However, on Windows, it is sometimes not possible to rename/move a - file to its destination file because the destination file is locked by another - process (e.g. antivirus software). For such situations, we now retry the save operation - on Windows. -# 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/9224 - -# 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/5862 diff --git a/changelog/fragments/1754944400-k8s-hints-env-vars-in-annotations.yaml b/changelog/fragments/1754944400-k8s-hints-env-vars-in-annotations.yaml deleted file mode 100644 index b0fc6f9f811..00000000000 --- a/changelog/fragments/1754944400-k8s-hints-env-vars-in-annotations.yaml +++ /dev/null @@ -1,4 +0,0 @@ -kind: bug-fix -summary: Correct hints annotations parsing to resolve only `${kubernetes.*}` placeholders instead of resolving all `${...}` patterns. -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/9307 diff --git a/changelog/fragments/1755059673-endpoint-28-not-fatal.yaml b/changelog/fragments/1755059673-endpoint-28-not-fatal.yaml deleted file mode 100644 index 74f031376e0..00000000000 --- a/changelog/fragments/1755059673-endpoint-28-not-fatal.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: Treat exit code 28 from Endpoint binary as non-fatal - -# 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/9320 - -# 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/1755076749-fix-jitter-backoff-strategy-reset.yaml b/changelog/fragments/1755076749-fix-jitter-backoff-strategy-reset.yaml deleted file mode 100644 index 3ce7a6c567b..00000000000 --- a/changelog/fragments/1755076749-fix-jitter-backoff-strategy-reset.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: Fixed jitter backoff strategy reset - -# 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/9342 - -# 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/8864 diff --git a/changelog/fragments/1755149089-update-otel-components-to-v0.130.0.yaml b/changelog/fragments/1755149089-update-otel-components-to-v0.130.0.yaml deleted file mode 100644 index b7862ee60fd..00000000000 --- a/changelog/fragments/1755149089-update-otel-components-to-v0.130.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.130.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/1755544412-Fix-default-constant-support-in-output-configuration.yaml b/changelog/fragments/1755544412-Fix-default-constant-support-in-output-configuration.yaml deleted file mode 100644 index 469661600d6..00000000000 --- a/changelog/fragments/1755544412-Fix-default-constant-support-in-output-configuration.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 Docker container failing to start with no matching vars: ${env.ELASTICSEARCH_API_KEY:} and similar errors by restoring support for `:` to set default values." - -# 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/9451 - -# 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/9328 diff --git a/changelog/fragments/1755547590-Upgrade-to-Go-1.24.6..yaml b/changelog/fragments/1755547590-Upgrade-to-Go-1.24.6..yaml deleted file mode 100644 index c63b709c029..00000000000 --- a/changelog/fragments/1755547590-Upgrade-to-Go-1.24.6..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: security - -# Change summary; a 80ish characters long description of the change. -summary: Upgrade to Go 1.24.6. - -# 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/9287 - -# 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/1755601979-deb-upgrade-stop-agent-service.yaml b/changelog/fragments/1755601979-deb-upgrade-stop-agent-service.yaml deleted file mode 100644 index 7b486eab8ea..00000000000 --- a/changelog/fragments/1755601979-deb-upgrade-stop-agent-service.yaml +++ /dev/null @@ -1,4 +0,0 @@ -kind: bug-fix -summary: Fix deb upgrade by stopping elastic-agent service before stopping endpoint -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/9462