You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,14 @@
2
2
3
3
All notable changes to this project will be documented in this file.
4
4
5
+
<!--
6
+
Do *NOT* add changelog entries here!
7
+
8
+
This changelog is managed by towncrier and is compiled at release time.
9
+
10
+
See https://github.com/open-telemetry/opentelemetry-python/blob/main/CONTRIBUTING.md#changelog for details.
11
+
-->
12
+
5
13
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
14
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
15
@@ -10,6 +18,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
10
18
> [!IMPORTANT]
11
19
> We are working on stabilizing the Log signal that would require making deprecations and breaking changes. We will try to reduce the releases that may require an update to your code, especially for instrumentations or for sdk developers.
12
20
21
+
<!-- changelog start -->
22
+
13
23
## Unreleased
14
24
15
25
- `opentelemetry-sdk`: fix multi-processor `force_flush` skipping remaining processors when one returns `None`
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,37 @@ You can run `tox` with the following arguments:
73
73
-`tox -e tracecontext` to run integration tests for tracecontext.
74
74
-`tox -e precommit` to run all `pre-commit` actions
75
75
76
+
### Changelog
77
+
78
+
This project uses [towncrier](https://towncrier.readthedocs.io/) to manage the changelog. Instead of editing `CHANGELOG.md` directly, each PR should include a changelog fragment file in the `.changelog/` directory.
79
+
80
+
**Creating a changelog fragment:**
81
+
82
+
Create a file named `.changelog/<PR_NUMBER>.<TYPE>` where `TYPE` is one of: `added`, `changed`, `deprecated`, `removed`, `fixed`.
83
+
84
+
The file should contain a one-line description of the change. For example, `.changelog/1234.added`:
85
+
86
+
```
87
+
`opentelemetry-sdk`: add support for new feature
88
+
```
89
+
90
+
**Writing a good changelog entry:**
91
+
92
+
- Write in imperative tone, as if completing the phrase "This change will..."
93
+
- Keep entries concise — ideally under 80 characters
94
+
- Prefix with the affected package name when applicable (e.g. `` `opentelemetry-sdk`: ... ``)
95
+
- Don't include the PR number — towncrier adds it automatically
96
+
97
+
**Preview the changelog:**
98
+
99
+
```console
100
+
towncrier build --draft --version Unreleased
101
+
```
102
+
103
+
The CI will verify that a changelog fragment exists and that `CHANGELOG.md` is not directly modified.
104
+
105
+
If your change does not need a changelog entry, add the "Skip Changelog" label to the PR.
106
+
76
107
`ruff check` and `ruff format` are executed when `tox -e ruff` is run. We strongly recommend you to configure [pre-commit](https://pre-commit.com/) locally to run `ruff` and `rstcheck` automatically before each commit by installing it as git hooks. You just need to [install pre-commit](https://pre-commit.com/#install) in your environment:
Copy file name to clipboardExpand all lines: RELEASING.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,7 @@
19
19
20
20
### Backporting
21
21
22
-
Creating manual backports of pull request(s) requires the `backport` label to be added in order to have a green CI. Even if there where
23
-
no changes on a repo the patch release preparation workflow requires an empty `## Unreleased` header in `CHANGELOG.md`.
24
-
25
-
Backport of pull request(s) can be automated by a workflow only if there where no changes that will create conflicts in the release
26
-
branch, unfortunately every `CHANGELOG.md` change will create one.
22
+
Creating manual backports of pull request(s) requires the `backport` label to be added in order to have a green CI.
27
23
28
24
To use the workflow to backport pull request(s) to the release branch:
29
25
* Run the [Backport workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/backport.yml).
@@ -33,8 +29,6 @@ To use the workflow to backport pull request(s) to the release branch:
33
29
* Add the label `backport` to the generated pull request.
34
30
* In case label automation doesn't work, just close and reopen the PR so that the workflow will take into account the label automation we have in place.
35
31
* Review and merge the backport pull request that it generates.
36
-
* Merge a pull request to the release branch updating the `CHANGELOG.md`.
37
-
* The heading for the unreleased entries should be `## Unreleased`.
0 commit comments