Repository navigation
[specs] release azure-http-specs 0.1.0-alpha.43 for 0.70.0 - #4897
Merged
Merged
Conversation
Republish azure-http-specs so its workspace peer ranges resolve to @azure-tools/typespec-azure-core@^0.70.0 and the TypeSpec 1.14.0 line, unblocking downstream emitter installs (e.g. @typespec/http-client-python). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
commit: |
Contributor
|
You can try these changes here
|
Yuchao Yan (msyyc)
marked this pull request as ready for review
July 15, 2026 02:10
Yuchao Yan (msyyc)
requested review from
Brian Terlson (bterlson),
Mark Cowlishaw (markcowl) and
Timothee Guerin (timotheeguerin)
as code owners
July 15, 2026 02:10
Yuchao Yan (msyyc)
approved these changes
Jul 15, 2026
Member
|
I remember there was always a new version for |
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.
Why
PR #4896 ("Prepare publish for 0.70.0") bumped
@azure-tools/typespec-azure-coreto0.70.0but did not bump@azure-tools/azure-http-specs, so it remains at0.1.0-alpha.42whose published peer is@azure-tools/typespec-azure-core@^0.69.0.As a result, the
@typespec/http-client-pythonrelease PR (microsoft/typespec#11252) failsnpm ciwith anERESOLVEpeer conflict:No published
azure-http-specs(public npm or the azure-sdk-for-js feed) currently accepts stable0.70.0.What
Bump
@azure-tools/azure-http-specsto0.1.0-alpha.43and republish. Itsworkspace:^peer ranges resolve againstmain(now on0.70.0/1.14.0), so the republished package carries@azure-tools/typespec-azure-core@^0.70.0and the1.14.0core peers.Draft for maintainer review of the release/publish process.