You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks that after generation we ran migrate-package command directly without running rush update so dev-tool failed to execute the npm run format command.
@wanlwanl I saw in some other automation run where typespec files was modified there's rush update before migrate-package. Do you know why it is not the same for the above run?
The text was updated successfully, but these errors were encountered:
It looks that after generation we ran migrate-package command directly without running rush update so dev-tool failed to execute the npm run format command.
I put migration step after rush update step for all sdk automations currently. Great, I can move migration step before rush update
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4553716&view=logs&j=47092895-c7c8-567a-c7a6-8c88f3ec178e&t=d293a8e8-c6af-5091-cdf7-4c66482dd6f2&l=328
It looks that after generation we ran migrate-package command directly without running
rush update
so dev-tool failed to execute thenpm run format
command.@wanlwanl I saw in some other automation run where typespec files was modified there's
rush update
before migrate-package. Do you know why it is not the same for the above run?The text was updated successfully, but these errors were encountered: