From cdde2ab5881768dc6d56a375ab32c4b14eaa3286 Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Mon, 11 Aug 2025 13:29:24 +0200 Subject: [PATCH 1/2] chore(repo): Adjust "Publishing a Release" document to include internal changes section in changelog --- docs/publishing-a-release.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/publishing-a-release.md b/docs/publishing-a-release.md index 3b952672e4e9..9f7a2ffbc963 100644 --- a/docs/publishing-a-release.md +++ b/docs/publishing-a-release.md @@ -44,8 +44,8 @@ These have also been documented via [Cursor Rules](../.cursor/rules/publishing-r 1. Run `yarn changelog` and copy everything. 2. Create a new section in the changelog with the previously determined version number. 3. Paste in the logs you copied earlier. -4. Delete any which aren't user-facing changes (such as docs or tests). -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. +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. +5. Any changes that are purely internal (e.g. internal refactors `ref` without user-facing changes, tests, chores, etc) should be put under a `
` block, where the `` heading is "Internal Changes" (see example). 6. Make sure the changelog entries are ordered alphabetically. 7. If any of the PRs are from external contributors, include underneath the commits `Work in this release contributed by . Thank you for your contributions!`. @@ -78,5 +78,13 @@ This feature ships updates to the span names and ops to better match OpenTelemet - fix(sveltekit): Export `vercelAIIntegration` from `@sentry/node` ([#16496](https://github.com/getsentry/sentry-javascript/pull/16496)) +
+ Internal Changes + +- ref(node): Split up incoming & outgoing http handling ([#17358](https://github.com/getsentry/sentry-javascript/pull/17358)) +- test(node): Enable additionalDependencies in integration runner ([#17361](https://github.com/getsentry/sentry-javascript/pull/17361)) + +
+ Work in this release was contributed by @agrattan0820. Thank you for your contribution! ``` From e52358c41655fdf73ff7c598871d5fd555817acd Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Mon, 11 Aug 2025 13:33:01 +0200 Subject: [PATCH 2/2] Update docs/publishing-a-release.md --- docs/publishing-a-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/publishing-a-release.md b/docs/publishing-a-release.md index 9f7a2ffbc963..810b180c3ba9 100644 --- a/docs/publishing-a-release.md +++ b/docs/publishing-a-release.md @@ -45,7 +45,7 @@ These have also been documented via [Cursor Rules](../.cursor/rules/publishing-r 2. Create a new section in the changelog with the previously determined version number. 3. Paste in the logs you copied earlier. 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. -5. Any changes that are purely internal (e.g. internal refactors `ref` without user-facing changes, tests, chores, etc) should be put under a `
` block, where the `` heading is "Internal Changes" (see example). +5. Any changes that are purely internal (e.g. internal refactors (`ref`) without user-facing changes, tests, chores, etc) should be put under a `
` block, where the `` heading is "Internal Changes" (see example). 6. Make sure the changelog entries are ordered alphabetically. 7. If any of the PRs are from external contributors, include underneath the commits `Work in this release contributed by . Thank you for your contributions!`.