Skip to content

Docs/clarify bulk changelog default#442

Merged
blynchbitovi merged 3 commits intomainfrom
docs/clarify-bulk-changelog-default
Feb 17, 2026
Merged

Docs/clarify bulk changelog default#442
blynchbitovi merged 3 commits intomainfrom
docs/clarify-bulk-changelog-default

Conversation

@blynchbitovi
Copy link
Contributor

Updated issue with bulk update and previously removed feature flag.

- Remove feature flag useBulkChangelogAPI
- Bulk changelog API is now the default behavior
- Remove legacy individual changelog fetching code path
- Tested and verified working in production environment

The bulk changelog API reduces API calls from N per issue to ~1 per 1000 issues,
significantly reducing rate limiting issues.
Document the research, implementation steps, and API details for the
bulk changelog feature that reduces rate limiting.
- Add clear documentation indicating bulk changelog API is the permanent default
- Mark fetchBulkChangelogs as ✅ DEFAULT IMPLEMENTATION in JSDoc
- Document that fetchRemainingChangelogsForIssues uses bulk API to prevent rate limiting
- Deprecate legacy fetchRemainingChangelogsForIssue (singular) function with @deprecated tag
- Add warnings that the legacy function causes rate limiting and should not be used

The bulk changelog API has been the default since implementation, batching up to 1000
issues per request instead of making individual API calls. This prevents 429 rate
limiting errors. These documentation changes clarify this is the permanent default
behavior, not a feature flag.
@joggrbot

This comment has been minimized.

@blynchbitovi blynchbitovi merged commit 2a42aa2 into main Feb 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments