[storage-common] Bump @azure/core-rest-pipeline to ^1.24.0#38848
Open
jeremymeng wants to merge 1 commit into
Open
[storage-common] Bump @azure/core-rest-pipeline to ^1.24.0#38848jeremymeng wants to merge 1 commit into
jeremymeng wants to merge 1 commit into
Conversation
storage-common depends on the new NodeBuffer type exported by @azure/core-rest-pipeline v1.24.0, so raise the minimum version range accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jeremymeng
requested review from
EmmaZhu,
XiaoningLiu,
blueww,
jiacfan,
ljian3377 and
vinjiang
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the @azure/storage-common runtime dependency on @azure/core-rest-pipeline to ensure the declared minimum version matches the code’s requirement for the NodeBuffer type (exported starting in @azure/core-rest-pipeline@1.24.0).
Changes:
- Bumped
@azure/core-rest-pipelinedependency range from^1.19.1to^1.24.0in@azure/storage-common.
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.
Packages impacted by this PR
@azure/storage-commonIssues associated with this PR
N/A
Describe the problem that is addressed by this PR
@azure/storage-commonrelies on the newly exportedNodeBuffertype from@azure/core-rest-pipeline, which was introduced in v1.24.0. The declared minimum version (^1.19.1) was below that, so consumers installing storage-common without a matching transitive resolution could end up with an older core-rest-pipeline that does not exportNodeBuffer. This raises the declared minimum to^1.24.0so the dependency contract matches what the code actually requires.What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Bump the minimum compatible range in
package.jsonto^1.24.0. This is the standard semver-friendly way to express a new minimum requirement without forcing an exact version.Are there test cases added in this PR? (If not, why?)
No. This is a dependency version range adjustment only; no behavior change in source.
Provide a list of related PRs (if any)
N/A
Command used to generate this PR:**(Applicable only to SDK release request PRs)
N/A
Checklists