diff --git a/changelog/8.9.0.asciidoc b/changelog/8.9.0.asciidoc new file mode 100644 index 000000000..87f3afd2a --- /dev/null +++ b/changelog/8.9.0.asciidoc @@ -0,0 +1,86 @@ +version: 8.9.0 +entries: + - kind: security + summary: Use verified base image for building Fleet Server binaries + description: "" + component: "" + pr: + - "2339" + issue: [] + timestamp: 1682696415 + file: + name: 1682696415-crossbuild.yaml + checksum: 159350f6e8e2e60912b5ca57c2d0ee3fe10b1026 + - kind: breaking-change + summary: API default error is now 500 + description: Up until now when any not expected error was encountered it resulted int Bad Request response.\n This is changing and any not expected error will return Internal Server Error while keeping most of the current behavior\n unchanged and returning Bad Request on expected failure paths (e.g. Agent Inactive, Missing Agent ID, Missing Auth Header). + component: "" + pr: + - "2531" + issue: + - "2417" + timestamp: 1683024407 + file: + name: 1683024407-API-default-error-is-now-500.yaml + checksum: 6db2475a1815378713dd450298d696612f02cf7c + - kind: bug-fix + summary: fix-action-seq-no + description: Fix for a bug where agent `action_seq_no` was overwritten with 0 if the `ackToken` was not provided. + component: "" + pr: + - "2582" + issue: + - "2519" + timestamp: 1684151814 + file: + name: 1684151814-fix-action-seq-no.yaml + checksum: aac8471c8947618ba2e4c5fb1b21887118e923ef + - kind: enhancement + summary: Expose prometheus metrics + description: | + Expose prometheus metrics on metrics listener (when enabled). + Ship prometheus metrics with 'apm.Tracer' when tracer is enabled. + component: "" + pr: + - "2610" + issue: + - "2542" + timestamp: 1684437851 + file: + name: 1684437851-Expose-prometheus-metrics.yaml + checksum: 000a7d7ed2bcdc226fe90a8bd69017d9283ee2f2 + - kind: feature + summary: File Delivery to integrations + description: "" + component: "" + pr: + - "2666" + issue: [] + timestamp: 1685985303 + file: + name: 1685985303-file-delivery.yaml + checksum: 6deab19091b7ba365fcd13a97116e9e4bec980ab + - kind: bug-fix + summary: Fix issue causing Fleet Server Agent to go offline after reboot + description: "" + component: "" + pr: [] + issue: + - "2431" + timestamp: 1686780651 + file: + name: 1686780651-reuse-error-channel.yaml + checksum: f751708694ae58d8fc8ca9824955f00e4469b75c + - kind: feature + summary: Add elastic-api-version header support + description: | + Introduce a new middleware that support elastic-apiversion header to allow versioning of the Fleet server APIs. + If the header is not provided we fallback to a default version. + component: "" + pr: + - "2677" + issue: [] + timestamp: 1686781749 + file: + name: 1686781749-Add-elastic-api-version-header-support.yaml + checksum: 92552debd29fc1ac10f3035641be24e037866779 diff --git a/changelog/8.9.0.yaml b/changelog/8.9.0.yaml new file mode 100644 index 000000000..87f3afd2a --- /dev/null +++ b/changelog/8.9.0.yaml @@ -0,0 +1,86 @@ +version: 8.9.0 +entries: + - kind: security + summary: Use verified base image for building Fleet Server binaries + description: "" + component: "" + pr: + - "2339" + issue: [] + timestamp: 1682696415 + file: + name: 1682696415-crossbuild.yaml + checksum: 159350f6e8e2e60912b5ca57c2d0ee3fe10b1026 + - kind: breaking-change + summary: API default error is now 500 + description: Up until now when any not expected error was encountered it resulted int Bad Request response.\n This is changing and any not expected error will return Internal Server Error while keeping most of the current behavior\n unchanged and returning Bad Request on expected failure paths (e.g. Agent Inactive, Missing Agent ID, Missing Auth Header). + component: "" + pr: + - "2531" + issue: + - "2417" + timestamp: 1683024407 + file: + name: 1683024407-API-default-error-is-now-500.yaml + checksum: 6db2475a1815378713dd450298d696612f02cf7c + - kind: bug-fix + summary: fix-action-seq-no + description: Fix for a bug where agent `action_seq_no` was overwritten with 0 if the `ackToken` was not provided. + component: "" + pr: + - "2582" + issue: + - "2519" + timestamp: 1684151814 + file: + name: 1684151814-fix-action-seq-no.yaml + checksum: aac8471c8947618ba2e4c5fb1b21887118e923ef + - kind: enhancement + summary: Expose prometheus metrics + description: | + Expose prometheus metrics on metrics listener (when enabled). + Ship prometheus metrics with 'apm.Tracer' when tracer is enabled. + component: "" + pr: + - "2610" + issue: + - "2542" + timestamp: 1684437851 + file: + name: 1684437851-Expose-prometheus-metrics.yaml + checksum: 000a7d7ed2bcdc226fe90a8bd69017d9283ee2f2 + - kind: feature + summary: File Delivery to integrations + description: "" + component: "" + pr: + - "2666" + issue: [] + timestamp: 1685985303 + file: + name: 1685985303-file-delivery.yaml + checksum: 6deab19091b7ba365fcd13a97116e9e4bec980ab + - kind: bug-fix + summary: Fix issue causing Fleet Server Agent to go offline after reboot + description: "" + component: "" + pr: [] + issue: + - "2431" + timestamp: 1686780651 + file: + name: 1686780651-reuse-error-channel.yaml + checksum: f751708694ae58d8fc8ca9824955f00e4469b75c + - kind: feature + summary: Add elastic-api-version header support + description: | + Introduce a new middleware that support elastic-apiversion header to allow versioning of the Fleet server APIs. + If the header is not provided we fallback to a default version. + component: "" + pr: + - "2677" + issue: [] + timestamp: 1686781749 + file: + name: 1686781749-Add-elastic-api-version-header-support.yaml + checksum: 92552debd29fc1ac10f3035641be24e037866779 diff --git a/changelog/fragments/1682696415-crossbuild.yaml b/changelog/fragments/1682696415-crossbuild.yaml deleted file mode 100644 index 8d9d81c8d..000000000 --- a/changelog/fragments/1682696415-crossbuild.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: Use verified base image for building Fleet Server binaries - -# 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; a word indicating the component this changeset affects. -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: 2339 - -# 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/1683024407-API-default-error-is-now-500.yaml b/changelog/fragments/1683024407-API-default-error-is-now-500.yaml deleted file mode 100644 index 2ea730064..000000000 --- a/changelog/fragments/1683024407-API-default-error-is-now-500.yaml +++ /dev/null @@ -1,33 +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: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: API default error is now 500 - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: Up until now when any not expected error was encountered it resulted int Bad Request response. -This is changing and any not expected error will return Internal Server Error while keeping most of the current behavior -unchanged and returning Bad Request on expected failure paths (e.g. Agent Inactive, Missing Agent ID, Missing Auth Header). - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; 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: 2531 - -# Issue number; 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: 2417 diff --git a/changelog/fragments/1684151814-fix-action-seq-no.yaml b/changelog/fragments/1684151814-fix-action-seq-no.yaml deleted file mode 100644 index afdbee0ae..000000000 --- a/changelog/fragments/1684151814-fix-action-seq-no.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-action-seq-no - -# 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: Fix for a bug where agent `action_seq_no` was overwritten with 0 if the `ackToken` was not provided. - -# Affected component; a word indicating the component this changeset affects. -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: 2582 - -# 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: 2519 diff --git a/changelog/fragments/1684437851-Expose-prometheus-metrics.yaml b/changelog/fragments/1684437851-Expose-prometheus-metrics.yaml deleted file mode 100644 index 6f867a9b4..000000000 --- a/changelog/fragments/1684437851-Expose-prometheus-metrics.yaml +++ /dev/null @@ -1,34 +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: Expose prometheus metrics - -# 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: | - Expose prometheus metrics on metrics listener (when enabled). - Ship prometheus metrics with apm.Tracer when tracer is enabled. - -# Affected component; a word indicating the component this changeset affects. -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: 2610 - -# 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: 2542 diff --git a/changelog/fragments/1685985303-file-delivery.yaml b/changelog/fragments/1685985303-file-delivery.yaml deleted file mode 100644 index 921bfe36d..000000000 --- a/changelog/fragments/1685985303-file-delivery.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: File Delivery to integrations - -# 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; a word indicating the component this changeset affects. -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: 2666 - -# 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/1686780651-reuse-error-channel.yaml b/changelog/fragments/1686780651-reuse-error-channel.yaml deleted file mode 100644 index e73f1e29e..000000000 --- a/changelog/fragments/1686780651-reuse-error-channel.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 issue causing Fleet Server Agent to go offline after reboot - -# 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; a word indicating the component this changeset affects. -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: 2697 - -# 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: 2431 diff --git a/changelog/fragments/1686781749-Add-elastic-api-version-header-support.yaml b/changelog/fragments/1686781749-Add-elastic-api-version-header-support.yaml deleted file mode 100644 index 3605ea54e..000000000 --- a/changelog/fragments/1686781749-Add-elastic-api-version-header-support.yaml +++ /dev/null @@ -1,34 +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: Add elastic-api-version header support - -# 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: | - Introduce a new middleware that support elastic-apiversion header to allow versioning of the Fleet server APIs. - If the header is not provided we fallback to a default version. - -# Affected component; a word indicating the component this changeset affects. -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: 2677 - -# 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