Add missing changelog to 0.98.0 (#2845)

* Add missing changelog to 0.98.0

Signed-off-by: Pavol Loffay <p.loffay@gmail.com>

* Fix

Signed-off-by: Pavol Loffay <p.loffay@gmail.com>

---------

Signed-off-by: Pavol Loffay <p.loffay@gmail.com>

CHANGELOG.md

@@ -11,6 +11,7 @@
 
 ### 🧰 Bug fixes 🧰
 
+- `target allocator`: Fix for keepequal/dropequal action (#2793)
 - `collector`: Create automatically the RBAC permissions to manage replicasets when using the k8sattributesprocessor (#2823)
 - `documentation`: The description for some fields was truncated in the documentation. (#2563)
 

RELEASE.md

@@ -2,22 +2,23 @@
 
 Steps to release a new version of the OpenTelemetry Operator:
 
-1. Set the version you're releasing as an environment variable for convenience: `export VERSION=0.n+1.0`
-2. Update `versions.txt`
-   - Operator, target allocator and opamp-bridge should be `$VERSION`.
-   - OpenTelemetry Collector should be the latest collector version. The `major.minor` should typically match, with the patch portion being possibly different.
-   - The `autoinstrumentation-*` versions should match the latest supported versions in `autoinstrumentation/`.
-     > [!WARNING]
-     > DO NOT BUMP JAVA PAST `1.32.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.
-3. Check if the compatible OpenShift versions are updated in the `hack/add-openshift-annotations.sh` script.
-4. Update the bundle by running `make bundle VERSION=$VERSION`.
-5. Change the compatibility matrix in the [readme](./README.md) file, using the OpenTelemetry Operator version to be released and the current latest Kubernetes version as the latest supported version. Remove the oldest entry.
-6. Update release schedule table, by moving the current release manager to the end of the table with updated release version.
-7. Add the changes to the changelog by running `make chlog-update VERSION=$VERSION`.
-8. Check the OpenTelemetry Collector's changelog and ensure migration steps are present in `pkg/collector/upgrade`
-9. Once the changes above are merged and available in `main`, a draft release will be automatically created. Publish it once the release workflows all complete.
-10. Update the operator version in the Helm Chart, as per the [release guide](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-operator/CONTRIBUTING.md)
-11. The GitHub Workflow, submits two pull requests to the Operator hub repositories. Make sure the pull requests are approved and merged.
+1. Create a `Prepare relese x.y.z` pull request with the following content:
+   1. Set the version you're releasing as an environment variable for convenience: `export VERSION=0.n+1.0`
+   1. Update `versions.txt`
+      - Operator, target allocator and opamp-bridge should be `$VERSION`.
+      - OpenTelemetry Collector should be the latest collector version. The `major.minor` should typically match, with the patch portion being possibly different.
+      - The `autoinstrumentation-*` versions should match the latest supported versions in `autoinstrumentation/`.
+        > [!WARNING]
+        > DO NOT BUMP JAVA PAST `1.32.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.
+   1. Check if the compatible OpenShift versions are updated in the `hack/add-openshift-annotations.sh` script.
+   1. Update the bundle by running `make bundle VERSION=$VERSION`.
+   1. Change the compatibility matrix in the [readme](./README.md) file, using the OpenTelemetry Operator version to be released and the current latest Kubernetes version as the latest supported version. Remove the oldest entry.
+   1. Update release schedule table, by moving the current release manager to the end of the table with updated release version.
+   1. Add the changes to the changelog by running `make chlog-update VERSION=$VERSION`.
+   1. Check the OpenTelemetry Collector's changelog and ensure migration steps are present in `pkg/collector/upgrade`
+1. Once the changes above are merged and available in `main`, a draft release will be automatically created. Publish it once the release workflows all complete.
+1. Update the operator version in the Helm Chart, as per the [release guide](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-operator/CONTRIBUTING.md)
+1. The GitHub Workflow, submits two pull requests to the Operator hub repositories. Make sure the pull requests are approved and merged.
     - `community-operators-prod` is used by OLM on OpenShift. Example: [`operator-framework/community-operators-prod`](https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/494)
     - `community-operators` is used by Operatorhub.io. Example: [`operator-framework/community-operators`](https://github.com/k8s-operatorhub/community-operators/pull/461)