eng, manual update on emitter-package.json devDependencies#39131
Merged
weidongxu-microsoft merged 1 commit intoMar 8, 2024
Merged
Conversation
Member
Author
|
/azp run java - openai |
|
Azure Pipelines successfully started running 1 pipeline(s). |
weidongxu-microsoft
marked this pull request as ready for review
March 8, 2024 02:03
weidongxu-microsoft
requested review from
JimSuplizio,
benbp,
hallipr and
weshaggard
as code owners
March 8, 2024 02:03
XiaofeiCao
approved these changes
Mar 8, 2024
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.
Usually we update emitter-package.json via automation.
But currently we still having problem with stream-style-serialization on 0.14.x, summarized in #39109
Therefore, we will continue use 0.13.x, with latest typespec libs.
The reason to bump typespec libs is that there is some bug fix in latest typespec libs. Also we'd better to have ours in sync with the package.json in spec repo.
In typespec-java peerDependencies, we use a version range. And there is no breaking change affect typespec-java from typespec 0.39.x to 0.40.0.