-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regenerate rush's shrinkwrap file #11621
Conversation
FYI you can accomplish the same thing with |
@willmtemple thanks for the tip! I created this issue: #11666. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with doing this as long as Engineering Systems approves. It'd be good to just run a few of our test pipelines on this PR as well.
/azp run js - storage-blob - tests |
No pipelines are associated with this pull request. |
/azp list |
No pipelines found for this repository. |
/azp run js - core - ci |
No pipelines are associated with this pull request. |
/azp list |
No pipelines found for this repository. |
/azp list |
/azp run js - storage-blob - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - text-analytics - tests |
No pipelines are associated with this pull request. |
/azp run js - textanalytics - tests |
No pipelines are associated with this pull request. |
/azp list |
No pipelines found for this repository. |
@mikeharder azp is acting weird again. |
@deyaaeldeen What are the next steps here? Anything blocking the PR? |
@ramya-rao-a The next step is to run the text analytics test in CI here but I am not able to, @mikeharder could you please do it? |
/azp run js - textanalytics - ci |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp where |
Azure DevOps orgs getting events for this repository: |
/azp list |
This change is not in trigger list for text analytics. Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run js - textanalytics - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
I just did:
rm common/config/rush/pnpm-lock.yaml
rush update
I think it is worth looking at a fresh regeneration. Or should we not have it checked-in at all?