Merge branch 'main' into patch-1

Author: emdneto

RELEASING.md

@@ -21,13 +21,16 @@
 > - opentelemetry-resource-detector-azure
 > - opentelemetry-sdk-extension-aws
 > - opentelemetry-instrumentation-openai-v2
+>
 > These libraries are also excluded from the general release.
 
 Package release preparation is handled by the [`[Package] Prepare release`](./.github/workflows/package-prepare-release.yml) workflow that allows
 to pick a specific package to release. It follows the same versioning strategy and process as the general release.
 
 Long-term package release branch follows `package-release/{package-name}/v{major}.{minor}.x` (or `package-release/{package-name}/v{major}.{minor}bx`) naming pattern.
 
+The workflow will create two pull requests, one against the `main` and one against the `package-release/` branch; both should be merged in order to proceed with the release.
+
 ## Preparing a new patch release
 
 * Backport pull request(s) to the release branch.
@@ -54,6 +57,8 @@ to pick a specific package to release.
 
 The workflow can only be run against long-term release branch such as `package-release/{package-name}/v{major}.{minor}.x` or `package-release/{package-name}/v{major}.{minor}bx`.
 
+The workflow will create a pull request that should be merged in order to proceed with the release.
+
 ## Making the release
 
 * Run the [Release workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/workflows/release.yml).

exporter/opentelemetry-exporter-prometheus-remote-write/test-requirements.txt

@@ -3,7 +3,7 @@ certifi==2024.7.4
 charset-normalizer==3.3.2
 # We can drop this after bumping baseline to pypy-39
 cramjam==2.1.0; platform_python_implementation == "PyPy"
-cramjam==2.8.1; platform_python_implementation != "PyPy"
+cramjam==2.8.4; platform_python_implementation != "PyPy"
 Deprecated==1.2.14
 idna==3.7
 iniconfig==2.0.0