Repository navigation
build(deps): @corbits/openai-responses moves from a git SHA pin to the npm release - #1080
Merged
Merged
Conversation
TheGreatAxios
force-pushed
the
cl-9690-openai-responses-npm
branch
from
October 1, 2026 14:32
19e44f2 to
af972db
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The root override for @corbits/openai-responses was a git SHA pin. It now uses the npm release ^0.2.1, and stays in overrides so the providers' transitive copies collapse onto it.
Finding: the pinned SHA (the initial release commit) is an ancestor of v0.2.1, so the pin is behind the tag, not ahead; the npm release supersedes it.
Changes: package.json override, bun.lock regenerated (one @corbits/openai-responses version, 0.2.1).
Verified: typecheck passes; @corbits/xai-provider imports from apps/hub.
Resolves CL-9690