Closed hallipr closed 4 months ago
When packages reference @typespec/xml and use typespec-bump-deps, other typespec packages are updated to dev versions, but @typespec/xml is not. This causes peer range collisions in other packages:
See: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3926894&view=logs&j=739bb7ec-7296-5b40-7dff-ee3297bfdaa4&t=164b9cb9-850d-5194-a052-63f5151be232&l=167
npm list --all npm error code ELSPROBLEMS npm error invalid: @typespec/compiler@0.58.0-dev.3 C:\Users\cloudtest\AppData\Local\Temp\tmpfn02gj.tmp\emitter-consumer\node_modules\@typespec\compiler ... +-- @typespec/versioning@0.58.0-dev.0 | `-- @typespec/compiler@0.58.0-dev.3 deduped `-- @typespec/xml@0.57.0 `-- @typespec/compiler@0.58.0-dev.3 deduped invalid: "~0.57.0" from node_modules/@typespec/xml
When packages reference @typespec/xml and use typespec-bump-deps, other typespec packages are updated to dev versions, but @typespec/xml is not. This causes peer range collisions in other packages:
See: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3926894&view=logs&j=739bb7ec-7296-5b40-7dff-ee3297bfdaa4&t=164b9cb9-850d-5194-a052-63f5151be232&l=167