Skip to content

[engSys] - Upgrade puppeteer#20782

Merged
maorleger merged 1 commit intoAzure:mainfrom
maorleger:upgrade-puppeteer
Mar 11, 2022
Merged

[engSys] - Upgrade puppeteer#20782
maorleger merged 1 commit intoAzure:mainfrom
maorleger:upgrade-puppeteer

Conversation

@maorleger
Copy link
Copy Markdown
Member

@maorleger maorleger commented Mar 11, 2022

Issues associated with this PR

Resolves #19234

Describe the problem that is addressed by this PR

Upgrades puppeteer to the latest version

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

I looked through the changelog for puppeteer and did not see any major changes between 10 and 13 that should impact us

Are there test cases added in this PR? (If not, why?)

No, this is a test dependency upgrade so if current tests pass we are good

Provide a list of related PRs (if any)

Command used to generate this PR: (Applicable only to SDK release request PRs)

rush add -p puppeeteer --dev --caret --make-consistent

Checklists

  • Added impacted package name to the issue description.
  • Does this PR need any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here.)
  • Added a changelog (if necessary).

Copy link
Copy Markdown
Member

@jeremymeng jeremymeng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for the upgrade

@maorleger maorleger merged commit 8d5a1b2 into Azure:main Mar 11, 2022
@maorleger maorleger deleted the upgrade-puppeteer branch March 11, 2022 20:02
WeiJun428 pushed a commit to WeiJun428/azure-sdk-for-js that referenced this pull request Mar 20, 2022
### Issues associated with this PR
Resolves Azure#19234 

### Describe the problem that is addressed by this PR
Upgrades puppeteer to the latest version

### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
I looked through the changelog for puppeteer and did not see any major changes between 10 and 13 that should impact us
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dependency package puppeteer has a new version available

3 participants