Repository navigation
[python] release new version - #11252
Merged
Merged
Conversation
|
You can try these changes here
|
Yuchao Yan (msyyc)
force-pushed
the
publish/python-release-07-14
branch
from
July 15, 2026 03:38
4700540 to
ccf0722
Compare
commit: |
Yuchao Yan (msyyc)
approved these changes
Jul 15, 2026
Yuchao Yan (msyyc)
enabled auto-merge
July 15, 2026 03:41
Chenxi Jiang (ChenxiJiang333)
approved these changes
Jul 15, 2026
Yuchao Yan (msyyc)
pushed a commit
to msyyc/typespec-azure
that referenced
this pull request
Jul 15, 2026
## Why PR Azure#4896 ("Prepare publish for 0.70.0") bumped `@azure-tools/typespec-azure-core` to `0.70.0` but did **not** bump `@azure-tools/azure-http-specs`, so it remains at `0.1.0-alpha.42` whose published peer is `@azure-tools/typespec-azure-core@^0.69.0`. As a result, the `@typespec/http-client-python` release PR (microsoft/typespec#11252) fails `npm ci` with an `ERESOLVE` peer conflict: ``` Found: @azure-tools/typespec-azure-core@0.70.0 peer @azure-tools/typespec-azure-core@"^0.69.0" from @azure-tools/azure-http-specs@0.1.0-alpha.42 ``` No published `azure-http-specs` (public npm or the azure-sdk-for-js feed) currently accepts stable `0.70.0`. ## What Bump `@azure-tools/azure-http-specs` to `0.1.0-alpha.43` and republish. Its `workspace:^` peer ranges resolve against `main` (now on `0.70.0` / `1.14.0`), so the republished package carries `@azure-tools/typespec-azure-core@^0.70.0` and the `1.14.0` core peers. Draft for maintainer review of the release/publish process. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
No description provided.