Repository navigation
build(deps): @corbits/credential-header moves from a git SHA pin to the npm release - #1082
Merged
Merged
Conversation
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.
apps/sidecar depended on @corbits/credential-header through a git SHA pin. It now uses the npm release ^0.1.0.
Finding: the library has no v0.1.0 tag. The pinned SHA is the initial import; the published 0.1.0 (gitHead 4b54a43) is three commits later (@intX 0.4.0 bump, dist build, readme). The pin is behind the published code, not ahead.
Changes: one package.json entry, bun.lock regenerated (one @corbits/credential-header version, 0.1.0).
Verified: typecheck passes; the package imports from apps/sidecar.
Resolves CL-9692