Upgrade emitter and TypeSpec packages to latest versions#25221
Merged
JiaqiZhang-Dev merged 2 commits intomainfrom Sep 11, 2025
Merged
Upgrade emitter and TypeSpec packages to latest versions#25221JiaqiZhang-Dev merged 2 commits intomainfrom
JiaqiZhang-Dev merged 2 commits intomainfrom
Conversation
Co-authored-by: JiaqiZhang-Dev <194873822+JiaqiZhang-Dev@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] upgrade emitter and tsp version
Upgrade emitter and TypeSpec packages to latest versions
Sep 11, 2025
JiaqiZhang-Dev
requested review from
ArcturusZhang,
RickWinter,
chlowell,
gracewilcox,
jhendrixMSFT,
lirenhe,
richardpark-msft and
tadelesh
as code owners
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR upgrades all TypeSpec-related packages in the emitter package configuration to their latest available versions, addressing issue #24780. The upgrade includes both production dependencies and development dependencies across the TypeSpec ecosystem.
- Updates the main TypeSpec Go tools dependency from 0.8.1 to 0.8.2
- Upgrades all Azure TypeSpec tools from 0.59.x versions to 0.60.0
- Updates core TypeSpec packages from 1.3.0/0.73.0 to 1.4.0/0.74.0 respectively
Files not reviewed (1)
- eng/emitter-package-lock.json: Language not supported
JiaqiZhang-Dev
approved these changes
Sep 11, 2025
tadelesh
approved these changes
Sep 11, 2025
Member
|
/check-enforcer evaluate |
lirenhe
approved these changes
Sep 11, 2025
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.
This PR upgrades all TypeSpec-related packages in
eng/emitter-package.jsonto their latest available versions as requested in the issue.Changes Made
The following packages were upgraded:
Dependencies:
@azure-tools/typespec-go: 0.8.1 → 0.8.2Dev Dependencies:
@azure-tools/typespec-autorest: 0.59.1 → 0.60.0@azure-tools/typespec-azure-core: 0.59.0 → 0.60.0@azure-tools/typespec-azure-resource-manager: 0.59.2 → 0.60.0@azure-tools/typespec-azure-rulesets: 0.59.0 → 0.60.0@azure-tools/typespec-client-generator-core: 0.59.1 → 0.60.0@typespec/compiler: 1.3.0 → 1.4.0@typespec/events: 0.73.0 → 0.74.0@typespec/http: 1.3.0 → 1.4.0@typespec/openapi: 1.3.0 → 1.4.0@typespec/rest: 0.73.0 → 0.74.0@typespec/sse: 0.73.0 → 0.74.0@typespec/streams: 0.73.0 → 0.74.0@typespec/versioning: 0.73.0 → 0.74.0@typespec/xml: 0.73.0 → 0.74.0Process Followed
npm-check-updates(ncu) to identify and upgrade packages to latest versions~or^prefixes)emitter-package-lock.jsonusingtsp-client generate-lock-filenode_modules) were included in the commitAll version specifications remain absolute as required, maintaining compatibility with the existing build process.
Fixes #24780.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.