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
M109 roll #9233
Labels
Comments
Nikolay, let's roll a version next week as M109 is soon promoted to beta. |
Lightning00Blade
added a commit
that referenced
this issue
Dec 7, 2022
Merged
OrKoN
pushed a commit
that referenced
this issue
Dec 7, 2022
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.4.0</summary> ## [19.4.0](puppeteer-v19.3.0...puppeteer-v19.4.0) (2022-12-07) ### Features * **chromium:** roll to Chromium 109.0.5412.0 (r1069273) ([#9364](#9364)) ([1875da6](1875da6)), closes [#9233](#9233) ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.3.0 to 19.4.0 </details> <details><summary>puppeteer-core: 19.4.0</summary> ## [19.4.0](puppeteer-core-v19.3.0...puppeteer-core-v19.4.0) (2022-12-07) ### Features * ability to send headers via ws connection to browser in node.js environment ([#9314](#9314)) ([937fffa](937fffa)), closes [#7218](#7218) * **chromium:** roll to Chromium 109.0.5412.0 (r1069273) ([#9364](#9364)) ([1875da6](1875da6)), closes [#9233](#9233) * **puppeteer-core:** keydown supports commands ([#9357](#9357)) ([b7ebc5d](b7ebc5d)) ### Bug Fixes * **puppeteer-core:** avoid type instantiation errors ([#9370](#9370)) ([17f31a9](17f31a9)), closes [#9369](#9369) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
M109 is going to beta on Thu, Dec 1, 2022 which is around the time we need to try rolling a new version.
TODOs:
cc @jrandolf @Lightning00Blade
The text was updated successfully, but these errors were encountered: