feat(github): split list_releases and add get_release tool #91
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses context overrun issues when using
list_releaseson repositories with many releases and large changelogs.Changes
Breaking Change
include_body_and_assetsparameter fromlist_releaseslist_releasesnow returns lightweight metadata only (id, name, tag_name, dates, draft/prerelease flags)New Tool
get_releasetool to fetch full details for a single release:release_id(number) ortag(string) to identify the releasehtml_urlfor direct linkingVersion Bump
@blink-sdk/githubfrom0.0.22→0.1.0Rationale
The previous design allowed fetching bodies and assets for many releases at once, which could result in 500KB+ responses for repos like
coder/coder(24 assets per release, ~1KB changelogs). This would blow the context window even on fresh chats.The new pattern:
get_releasewhen you need the detailsFixes #83