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: docs/publishing-a-release.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,8 @@ These have also been documented via [Cursor Rules](../.cursor/rules/publishing-r
44
44
1. Run `yarn changelog` and copy everything.
45
45
2. Create a new section in the changelog with the previously determined version number.
46
46
3. Paste in the logs you copied earlier.
47
-
4.Delete any which aren't user-facing changes (such as docs or tests).
48
-
5.If there are any important features or fixes, highlight them under the `Important Changes` subheading. If there are no important changes, don't include this section. If the `Important Changes` subheading is used, put all other changes under the `Other Changes` subheading.
47
+
4.If there are any important features or fixes, highlight them under the `Important Changes` subheading. If there are no important changes, don't include this section. If the `Important Changes` subheading is used, put all other user-facing changes under the `Other Changes` subheading.
48
+
5.Any changes that are purely internal (e.g. internal refactors (`ref`) without user-facing changes, tests, chores, etc) should be put under a `<details>` block, where the `<summary>` heading is "Internal Changes" (see example).
49
49
6. Make sure the changelog entries are ordered alphabetically.
50
50
7. If any of the PRs are from external contributors, include underneath the commits
51
51
`Work in this release contributed by <list of external contributors' GitHub usernames>. Thank you for your contributions!`.
@@ -78,5 +78,13 @@ This feature ships updates to the span names and ops to better match OpenTelemet
78
78
79
79
- fix(sveltekit): Export `vercelAIIntegration` from `@sentry/node` ([#16496](https://github.com/getsentry/sentry-javascript/pull/16496))
0 commit comments