chore: prepare 4.0.0 release

CHANGELOG.md

@@ -7,63 +7,10 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 <!-- towncrier release notes start -->
 
-## [v3.16.1]
+## [v4.0.0]
 
 ### Released 2023-10-20
 
-### Changed
-
-- chore: upgrade otel to 0.87.0-sumo-0 [#3334]
-
-[#3334]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3334
-[v3.16.1]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v3.16.1
-
-## [v3.16.0]
-
-### Released 2023-10-18
-
-- feat(metrics): allow overriding metrics collector configuration [#3314]
-
-### Changed
-
-- chore: update setup job to `v3.11.0` [#3320]
-
-### Fixed
-
-- fix(logs)!: move JSON parsing after user-defined processors [#3281]
-
-  The log body will now always be a string if accessed in extra processors. Users who want to access specific fields in their parsed JSON
-  log should explicitly call ParseJSON in their processor definition.
-
-- fix(metrics): decompose OTLP histograms [#3289]
-- fix(metrics): drop stale datapoints [#3318]
-- fix: fix Otel Operator installation with Helm 3.13 [#3321]
-- fix(metrics): kube-state-metrics pod metadata [#3323]
-
-[#3314]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3314
-[#3320]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3320
-[#3318]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3318
-[#3321]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3321
-[#3323]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3323
-[v3.16.0]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v3.16.0
-
-## [v4.0.0-rc.1]
-
-### Released 2023-09-28
-
-### Fixed
-
-- fix(openshift): fix SecurityContextConstraints [#3308] [#3309] [#3310]
-
-[#3308]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3308
-[#3309]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3309
-[#3310]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3310
-[v4.0.0-rc.1]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v4.0.0-rc.1
-
-## [v4.0.0-rc.0]
-
-### Released 2023-09-26
-
 ### Migration from v3
 
 See the [migration guide][v4_migration_guide] for details.
@@ -76,24 +23,24 @@ See the [migration guide][v4_migration_guide] for details.
 - feat!: use OTLP sources by default [#3297]
 - feat!(metrics): move extra processors after sumologic_schema [#3306]
 - fix(metrics)!: drop k8s.node.name attribute [#3295]
-- fix(logs)!: move JSON parsing after user-defined processors [#3281]
-
-  The log body will now always be a string if accessed in extra processors. Users who want to access specific fields in their parsed JSON
-  log should explicitly call ParseJSON in their processor definition.
+- feat!: enable autoscaling by default [#3329]
 
 ### Added
 
 - feat(logs): add `sumologic.logs.additionalFields` property [#3286]
 - feat(metrics): add additionalServiceMonitors setting [#3292]
+- feat(metrics): collect node_memory_MemAvailable_bytes [#3322]
+- chore: add support for k8s 1.27 with KOPS [#3332]
 
 ### Changed
 
 - feat(prometheus): Removing prometheus recording rules [#3211]
 - feat(metrics): move app metrics filtering to metadata layer [#3232]
+- chore: drop support for GKE with k8s 1.23 [#3340]
 
 ### Fixed
 
-- fix(metrics): decompose OTLP histograms [#3289]
+- fix(openshift): fix SecurityContextConstraints [#3308] [#3309] [#3310]
 
 [#3244]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3244
 [#3248]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3248
@@ -107,8 +54,54 @@ See the [migration guide][v4_migration_guide] for details.
 [#3281]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3281
 [#3289]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3289
 [#3295]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3295
+[#3308]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3308
+[#3309]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3309
+[#3310]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3310
+[#3329]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3329
+[#3322]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3322
+[#3332]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3332
+[#3340]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3340
+[v4.0.0]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v4.0.0
 [v4_migration_guide]: /docs/v4-migration-doc.md
-[v4.0.0-rc.0]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v4.0.0-rc.0
+
+## [v3.16.1]
+
+### Released 2023-10-20
+
+### Changed
+
+- chore: upgrade otel to 0.87.0-sumo-0 [#3334]
+
+[#3334]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3334
+[v3.16.1]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v3.16.1
+
+## [v3.16.0]
+
+### Released 2023-10-18
+
+### Changed
+
+- chore: update setup job to `v3.11.0` [#3320]
+- feat(metrics): allow overriding metrics collector configuration [#3314]
+
+### Fixed
+
+- fix(logs)!: move JSON parsing after user-defined processors [#3281]
+
+  The log body will now always be a string if accessed in extra processors. Users who want to access specific fields in their parsed JSON
+  log should explicitly call ParseJSON in their processor definition.
+
+- fix(metrics): decompose OTLP histograms [#3289]
+- fix(metrics): drop stale datapoints [#3318]
+- fix: fix Otel Operator installation with Helm 3.13 [#3321]
+- fix(metrics): kube-state-metrics pod metadata [#3323]
+
+[#3314]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3314
+[#3320]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3320
+[#3318]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3318
+[#3321]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3321
+[#3323]: https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/3323
+[v3.16.0]: https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/v3.16.0
 
 ## [v3.15.0]
 

README.md

@@ -22,7 +22,8 @@ release.
 
 | version                                                                                                 | planned end of life date |
 | ------------------------------------------------------------------------------------------------------- | ------------------------ |
-| [v3.16](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/release-v3.16/docs/README.md) | TBA                      |
+| [v4.0](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/release-v4.0/docs/README.md)   | TBA                      |
+| [v3.16](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/release-v3.16/docs/README.md) | 2024-04-20               |
 | [v3.15](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/release-v3.15/docs/README.md) | 2024-04-18               |
 | [v3.14](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/release-v3.14/docs/README.md) | 2024-03-18               |
 | [v3.13](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/release-v3.13/docs/README.md) | 2024-03-01               |

deploy/helm/sumologic/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v2
 name: sumologic
-version: 4.0.0-rc.1
-appVersion: 4.0.0-rc.1
+version: 4.0.0
+appVersion: 4.0.0
 description: A Helm chart for collecting Kubernetes logs, metrics, traces and events into Sumo Logic.
 type: application
 keywords: