Skip to content

Consider Publishing Generator Dev Versions When Running RegenPreview #11279

Description

As part of our developer loop, we run a regen preview pipeline that invokes https://github.com/microsoft/typespec/blob/main/packages/http-client-csharp/eng/scripts/Submit-AzureSdkForNetPr.ps1. This regenerates both unbranded data plane and azure branded data plane libraries from https://github.com/Azure/azure-sdk-for-net. The resulting PR (example contains the diffs from the regeneration but the CI in the pipeline always fails because the package.json files were updated to use local artifacts versions created on the host machine.

We should consider publishing these artifacts to the registry configured in the .npmrc, then referencing that published version in each relevant package.json file. That way, CI can run in the resulting pr

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

emitter:client:csharpIssue for the C# client emitter: @typespec/http-client-csharpfeatureNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions