diff --git a/changelog/8.6.0.yaml b/changelog/8.6.0.yaml
new file mode 100644
index 00000000000..625d6601a4d
--- /dev/null
+++ b/changelog/8.6.0.yaml
@@ -0,0 +1,215 @@
+version: 8.6.0
+entries:
+    - kind: feature
+      summary: Only support elasticsearch as an output for the beta synthetics integration.
+      description: ""
+      component: synthetics-integration
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1491
+      issue: []
+      timestamp: 1665780486
+      file:
+        name: 1665780486-heartbeat-es-output-only.yaml
+        checksum: 361f993ba3220aef531f7949308e61d2cbf82e03
+    - kind: feature
+      summary: Upgrade node to 18.12.0
+      description: ""
+      component: ""
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1657
+      issue: []
+      timestamp: 1667243040
+      file:
+        name: 1667243040-Upgrade-node-to-18.12.0.yaml
+        checksum: 38b5473e0ee1165ad9c5d74ee969a9228c3fa68a
+    - kind: feature
+      summary: Add experimental support for running the elastic-agent-shipper
+      description: ""
+      component: ""
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1527
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/219
+      timestamp: 1667571017
+      file:
+        name: 1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml
+        checksum: b2f5a0a8f9933c9ee624457116295aa674ef2a23
+    - kind: feature
+      summary: Add support for the Common Expression Language (CEL) Filebeat input type.
+      description: ""
+      component: spec
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1719
+      issue: []
+      timestamp: 1668483030
+      file:
+        name: 1668483030-common-expression-language.yaml
+        checksum: 82427fc514372c067e140837177c8d81131ed424
+    - kind: feature
+      summary: Collect logs from sub-processes via stdout and stderr and write them to a single, unified Elastic Agent log file.
+      description: ""
+      component: ""
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1702
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/221
+      timestamp: 1669236059
+      file:
+        name: 1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml
+        checksum: b4cf9cff0ef13bd168cadc80f89c4969b49fb378
+    - kind: bug-fix
+      summary: Elastic-agent will use local port when running fleet-server
+      description: The elastic-agent will now use the 8221 locally bound port when running fleet-server instead of the external port (8220).
+      component: ""
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1867
+      issue:
+        - https://github.com/elastic/ingest-dev/issues/1394
+      timestamp: 1669929902
+      file:
+        name: 1669929902-fix-local-fleet-server-port.yaml
+        checksum: 94f37fd1ff74bd320ec25cfcf2e2a0890eda494a
+    - kind: feature
+      summary: Remove inputs when all streams are removed
+      description: ""
+      component: ""
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1869
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/1868
+      timestamp: 1669940990
+      file:
+        name: 1669940990-Remove-inputs-when-all-streams-are-removed.yaml
+        checksum: 3fcf26a5bbb988db85c0c5923d4bd2284dc95866
+    - kind: feature
+      summary: No longer restart Elastic Agent on log level change
+      description: ""
+      component: ""
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1914
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/1896
+      timestamp: 1670518841
+      file:
+        name: 1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml
+        checksum: 12b34904cd47182a45e6e113518ef91ec718ebac
+    - kind: breaking-change
+      summary: Each input in an agent policy must have a unique ID.
+      description: |
+        Each input in an agent policy must have a unique ID, like "id: my-unique-input-id".
+        This only affects standalone agents. Unique IDs are automatically generated in
+        agent policies managed by Fleet.
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1994
+      issue: []
+      timestamp: 1671748292
+      file:
+        name: 1671748292-input-ids-are-required.yaml
+        checksum: 3ca6d7c10ce16c72c74b67b18916407ad09459fd
+    - kind: feature
+      summary: New control protocol between the Elastic Agent and its subprocesses.
+      description: |
+        New control protocol between the Elastic Agent and its subprocesses. 
+        Enables per integration health reporting and simplifies new input development, among other things.
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1701
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/836
+      timestamp: 1672911992
+      file:
+        name: 1672911992-v2-control-protocol.yaml
+        checksum: 837bf1d3f02ab63b94b5fbe5853b8163aaeb6f31
+    - kind: feature
+      summary: Internal directory structure change
+      description: Addition of the components directory (and removal of the downloads directory) to contain binaries and their associated artifacts.
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1701
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/836
+      timestamp: 1672911993
+      file:
+        name: 1672911993-v2-directory.yaml
+        checksum: 6ab87446b15a94993186754952e08c00a72c13ba
+    - kind: feature
+      summary: All binaries for every supported integration will be bundled in the Elastic Agent by default.
+      description: ""
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent-shipper/pull/126
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/836
+      timestamp: 1672911994
+      file:
+        name: 1672911994-v2-packaging.yaml
+        checksum: b6ae49ca5e99b94901d9585d1c21d326065a5cc6
+    - kind: breaking-change
+      summary: |
+        Diagnostic: --pprof argument has been removed, it's now always provided.
+      description: |
+        The diagnostic command is gathering diagnostic information about the Elastic Agent and each
+        component/unit ran by the Elastic Agent. --pprof argument has been removed: it's now always provided.
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1140
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/836
+      timestamp: 1672911995
+      file:
+        name: 1672911995-v2-diagnostic.yaml
+        checksum: 2ca011d608585e5b81446389da7590c0aecada7b
+    - kind: feature
+      summary: |
+        Add inspect components command to inspect the computed components/units model of the current configuration (elastic-agent inspect components).
+      description: ""
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1701
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/836
+      timestamp: 1672911997
+      file:
+        name: 1672911997-v2-inspect.yaml
+        checksum: 464bdde8aaadcd25590b89165d32131f4a4b168c
+    - kind: enhancement
+      summary: |
+        Health Status: Elastic Agent now indicates detailed status information for each component/unit.
+      description: ""
+      component: agent
+      pr:
+        - https://github.com/elastic/fleet-server/pull/1747
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/100
+      timestamp: 1672911999
+      file:
+        name: 1672911999-v2-health-status.yaml
+        checksum: eeb54c42273e877893abda9f56a92c2d31c4fa46
+    - kind: bug-fix
+      summary: Preserve persistent input state during upgrades.
+      description: |
+        Correctly preserve the Filebeat registry and other persistent input state during upgrades.
+        Eliminates event duplication after Elastic agent upgrades.
+      component: agent
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/1701
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/836
+      timestamp: 1672912001
+      file:
+        name: 1672912001-fix-duplicate-entries-on-upgrade.yaml
+        checksum: 4a06860accf7fcbae88034b9aaf669445071168e
+    - kind: known-issue
+      summary: |
+        OSQuery live query results can take up to 5 mins to show up in Kibana
+      description: ""
+      component: osquery
+      pr:
+        - https://github.com/elastic/elastic-agent/pull/2076
+      issue:
+        - https://github.com/elastic/elastic-agent/issues/2066
+      timestamp: 1672912002
+      file:
+        name: 1672912002-osquery-known-issue.yaml
+        checksum: e0f4d4d25322bd42298f080c62f9a86c361e7af1
diff --git a/changelog/fragments/1665780486-heartbeat-es-output-only.yaml b/changelog/fragments/1665780486-heartbeat-es-output-only.yaml
deleted file mode 100644
index 1e3b4059ddf..00000000000
--- a/changelog/fragments/1665780486-heartbeat-es-output-only.yaml
+++ /dev/null
@@ -1,31 +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: Only support elasticsearch as an output for the beta synthetics integration.
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-# description: 
-
-# Affected component; a word indicating the component this changeset affects.
-component: synthetics-integration
-
-# 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: 1491
-
-# 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: 1234
diff --git a/changelog/fragments/1666095433-service_runtime_v2.yaml b/changelog/fragments/1666095433-service_runtime_v2.yaml
deleted file mode 100644
index f54aa7e5d9c..00000000000
--- a/changelog/fragments/1666095433-service_runtime_v2.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-kind: feature
-summary: Service runtime for V2
-description: Service runtime for V2, tailored specifically for Endpoint service.
-pr: 1529
-issue: 1069
diff --git a/changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml b/changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml
deleted file mode 100644
index a670ebab9cb..00000000000
--- a/changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml
+++ /dev/null
@@ -1,31 +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: Upgrade node to 18.12.0
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1234
-
-# 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: 1234
diff --git a/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml b/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml
deleted file mode 100644
index 26430b05741..00000000000
--- a/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml
+++ /dev/null
@@ -1,31 +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 experimental support for running the elastic-agent-shipper
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1527
-
-# 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: 219
diff --git a/changelog/fragments/1668483030-common-expression-language.yaml b/changelog/fragments/1668483030-common-expression-language.yaml
deleted file mode 100644
index 824d7f5a501..00000000000
--- a/changelog/fragments/1668483030-common-expression-language.yaml
+++ /dev/null
@@ -1,31 +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 Common Expression Language input mapping to the Filebeat spec.
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# Affected component; a word indicating the component this changeset affects.
-component: spec
-
-# 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: 1719
-
-# 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: 1234
diff --git a/changelog/fragments/1668591286-fix-beats-logs.yaml b/changelog/fragments/1668591286-fix-beats-logs.yaml
deleted file mode 100644
index b9f749b12dc..00000000000
--- a/changelog/fragments/1668591286-fix-beats-logs.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: "monitoring: fix JSON logs parsing for Beats"
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-description: >-
-  Fixes the JSON parsing from Beats logs. The configuration sent to
-  Filebeat did not contain the input type, hence a log input instead of a
-  filestream one was being started.
-
-  This commit also improves the configuraiton of the ndjson parser.
-
-# Affected component; a word indicating the component this changeset affects.
-component: monitoring
-
-# 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: 1735
-
-# 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: 1234
diff --git a/changelog/fragments/1668645651-apm-fleet-config.yaml b/changelog/fragments/1668645651-apm-fleet-config.yaml
deleted file mode 100644
index 1e7738f43af..00000000000
--- a/changelog/fragments/1668645651-apm-fleet-config.yaml
+++ /dev/null
@@ -1,31 +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: V2 Provide fleet configuration to APM server
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1234
-
-# 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: 1737
diff --git a/changelog/fragments/1668679987-apm-monitoring.yaml b/changelog/fragments/1668679987-apm-monitoring.yaml
deleted file mode 100644
index fed7afe9177..00000000000
--- a/changelog/fragments/1668679987-apm-monitoring.yaml
+++ /dev/null
@@ -1,31 +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: apm-monitoring
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1234
-
-# 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: 1234
diff --git a/changelog/fragments/1669066497-struct-compare-unit-update.yaml b/changelog/fragments/1669066497-struct-compare-unit-update.yaml
deleted file mode 100644
index b907a4dd97d..00000000000
--- a/changelog/fragments/1669066497-struct-compare-unit-update.yaml
+++ /dev/null
@@ -1,31 +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: change config comparison to fix false unit update events
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# Affected component; a word indicating the component this changeset affects.
-component: runtime
-
-# 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: 1766
-
-# 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: 1738
diff --git a/changelog/fragments/1669159455-reimplement-processes-route.yaml b/changelog/fragments/1669159455-reimplement-processes-route.yaml
deleted file mode 100644
index 574fdeedf83..00000000000
--- a/changelog/fragments/1669159455-reimplement-processes-route.yaml
+++ /dev/null
@@ -1,31 +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: reimplement processes route
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-description: Re-implement processes route to restore compatibility with the current cloud health checks
-
-# 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: 1773
-
-# 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: 1731
diff --git a/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml b/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml
deleted file mode 100644
index 8dfa6a9aa2f..00000000000
--- a/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml
+++ /dev/null
@@ -1,31 +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: Capture stdout/stderr of all spawned components and adjust default log level to info for all components
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1702
-
-# 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: 221
diff --git a/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml b/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml
deleted file mode 100644
index a4bce27d801..00000000000
--- a/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml
+++ /dev/null
@@ -1,31 +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 Elastic-Agent fails to re-start during upgrade
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1805
-
-# 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: 1788
diff --git a/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml b/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml
deleted file mode 100644
index dbb33904f23..00000000000
--- a/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml
+++ /dev/null
@@ -1,31 +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 erroneous http url directory created for monitoring
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1811
-
-# 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: 1234
diff --git a/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml b/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml
deleted file mode 100644
index b97530312d4..00000000000
--- a/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml
+++ /dev/null
@@ -1,31 +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: Fix osqueryd and osquery-extension.ext permissions
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1829
-
-# 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: 1234
diff --git a/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml b/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml
deleted file mode 100644
index c693e26a7f5..00000000000
--- a/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml
+++ /dev/null
@@ -1,31 +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 agent logging level to fleet configuration
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1856
-
-# 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: 1853
diff --git a/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml b/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml
deleted file mode 100644
index f903beb0c11..00000000000
--- a/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml
+++ /dev/null
@@ -1,31 +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: Ensure unique input ID when variable substition occurs from a dynamic provider
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1866
-
-# 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: 1751
diff --git a/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml b/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml
deleted file mode 100644
index 08119ec5ac6..00000000000
--- a/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml
+++ /dev/null
@@ -1,31 +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: elastic-agent will use local port when running fleet-server
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-description: The elastic-agent will now use the 8221 locally bound port when running fleet-server instead of the external port (8220).
-
-# 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: 1234
-
-# 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: 1234
diff --git a/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml b/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml
deleted file mode 100644
index 070cb9a6f52..00000000000
--- a/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml
+++ /dev/null
@@ -1,31 +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: Remove inputs when all streams are removed
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1869
-
-# 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: 1868
diff --git a/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml b/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml
deleted file mode 100644
index 94de9883c23..00000000000
--- a/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml
+++ /dev/null
@@ -1,31 +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: No longer restart Elastic Agent on log level change
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-#description:
-
-# 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: 1914
-
-# 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: 1234
diff --git a/changelog/fragments/1671748292-input-ids-are-required.yaml b/changelog/fragments/1671748292-input-ids-are-required.yaml
deleted file mode 100644
index b14524c4352..00000000000
--- a/changelog/fragments/1671748292-input-ids-are-required.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: breaking-change
-
-# Change summary; a 80ish characters long description of the change.
-summary: Each input in an agent policy must have a unique ID.
-
-# Long description; in case the summary is not enough to describe the change
-# this field accommodate a description without length limits.
-description: |
-  Each input in an agent policy must have a unique ID, like "id: my-unique-input-id".
-  This only affects standalone agents. Unique IDs are automatically generated in
-  agent policies managed by Fleet.
-
-# Affected component; a word indicating the component this changeset affects.
-component: 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