chore(release): Add generate-changelog script by s1gr1d · Pull Request #18999 · getsentry/sentry-javascript

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

s1gr1d · 2026-01-27T14:28:24Z

I know we'll be using the craft release notes soon, but this can be beneficial for the time being. I've never had a lot of luck with the cursor command and this deterministic script might help other people as well.

Closes#19000 (added automatically)

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-27T14:37:40Z

+ const processDetailsContent = (): void => {
+ for (const line of detailsContent) {
+ const trimmed = line.trim();
+ if (trimmed.startsWith('-') && trimmed.includes('(#')) {


Internal changelog entries missed due to incorrect PR format check
Medium Severity
The check trimmed.includes('(#') in processDetailsContent fails to match entries with the markdown link format. The actual changelog format is ([#18750](url)) where [ appears between ( and #, so the substring (# is never present. This causes internal entries from <details> blocks to be silently ignored - they won't appear in output and their PR numbers won't be tracked in changelogPRs, potentially leading to duplicate entries when the same commits exist in the git log.

cursor · 2026-01-27T14:37:40Z

+ } else {
+ otherChanges.push(entry);
+ }
+ }


Missing PR tracking causes duplicate git commit entries
Medium Severity
The duplicate detection logic checks if a PR number exists in changelogPRs but never adds newly processed PR numbers to the set. If multiple commits in the git log reference the same PR number (which can happen with cherry-picks or amended commits), all of them will be added to the output as duplicates. After adding each commit's entry, its prNumber needs to be added to changelogPRs to prevent subsequent commits with the same PR from also being included.

github-actions · 2026-01-27T14:38:31Z

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,164	-	9,205	-0%
GET With Sentry	1,673	18%	1,743	-4%
GET With Sentry (error only)	6,003	66%	6,188	-3%
POST Baseline	1,167	-	1,207	-3%
POST With Sentry	559	48%	589	-5%
POST With Sentry (error only)	1,019	87%	1,051	-3%
MYSQL Baseline	3,259	-	3,349	-3%
MYSQL With Sentry	399	12%	479	-17%
MYSQL With Sentry (error only)	2,587	79%	2,706	-4%

View base workflow run

JPeer264

Let's try this out in the next release. LGTM

chore(release): Add generate-changelog script
fff95a4

s1gr1d requested a review from andreiborza January 27, 2026 14:28

github-actionsBot mentioned this pull request Jan 27, 2026
chore(release): Add generate-changelog script #19000
Closed

s1gr1d requested a review from Lms24 January 27, 2026 14:28

cursorBot reviewed Jan 27, 2026
View reviewed changes

JPeer264 approved these changes Jan 28, 2026
View reviewed changes

s1gr1d merged commit 4ae412c into developJan 28, 2026
216 checks passed

s1gr1d deleted the sig/generate-changelog branch January 28, 2026 13:33

This was referenced Jan 29, 2026
Update dependency @sentry/browser to v10.39.0 danielemery/quizlord-client#276
Merged
Update sentry-javascript monorepo to v10.38.0 danielemery/quizlord-api#399
Merged

This was referenced Jan 30, 2026
Update Backend dependencies (major) EcrituresNumeriques/stylo#1818
Closed
Update React dependencies (major) EcrituresNumeriques/stylo#1822
Closed

This was referenced Jan 30, 2026
chore(deps): update JavaScript SDK to v10.38.0 getsentry/sentry-dart#3474
Merged
chore(deps): update JavaScript SDK to v10.38.0 getsentry/sentry-react-native#5596
Merged
chore(deps): update JavaScript SDK to v10.57.0 Aetonix/sentry-react-native#3
Open

github-actionsBot mentioned this pull request Feb 17, 2026
chore(deps): update Sentry JavaScript to v10.39.0 getsentry/sentry-godot#527
Merged

This was referenced Feb 19, 2026
chore(deps): update services and utilities minor and patch updates vzauartcc/api#207
Closed
chore(deps): update dependency @sentry/react to v10.39.0 giantswarm/backstage#1286
Merged

WomB0ComB0 mentioned this pull request Feb 23, 2026
fix(deps): update dependency @sentry/nextjs to v10.39.0 WomB0ComB0/portfolio#390
Merged
1 task

have-renovateBot mentioned this pull request Feb 23, 2026
chore(deps): update @sentry/node to v10 happyvertical/sdk#827
Merged
1 task

This was referenced Feb 23, 2026
chore(deps): update services and utilities minor and patch updates vzauartcc/api#214
Merged
Update dependency @sentry/vue to v10.40.0 PBH-BTN/PeerBanHelper#1697
Merged

dev-mend-for-github-comBot mentioned this pull request Feb 25, 2026
chore(deps): update dependency @sentry/nextjs to v10 amaybaum-dev/AutoGPT#8
Open

staging-whitesource-for-github-comBot mentioned this pull request Feb 26, 2026
chore(deps): update dependency @sentry/nextjs to v10 - autoclosed amaybaum-staging/AutoGPT#13
Closed

mend-for-github-comBot mentioned this pull request Feb 26, 2026
chore(deps): update dependency @sentry/nextjs to v10.28.0 rsoreq-mend/AutoGPT#108
Open
1 task

github-actionsBot mentioned this pull request Mar 4, 2026
chore(deps): update dependency @sentry/browser to v10 ForumViriumHelsinki/OLMap#73
Open
1 task

renovateBot mentioned this pull request Mar 17, 2026
Update dependency @sentry/vue to v10 dandi/dandi-archive#2736
Merged
1 task

renovateBot mentioned this pull request Mar 26, 2026
fix(deps): update sentry to v10.43.0 treeverse/dvc.org#5551
Merged
1 task