Skip to content

Conversation

@snyk-bot
Copy link

Snyk has created this PR to upgrade @types/puppeteer from 3.0.1 to 3.0.6.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 5 versions ahead of your current version.
  • The recommended version was released a month ago, on 2021-07-07.
Release notes
Package name: @types/puppeteer
  • 3.0.6 - 2021-07-07
  • 3.0.5 - 2020-11-03
  • 3.0.4 - 2020-10-31
  • 3.0.3 - 2020-10-30
  • 3.0.2 - 2020-09-08
  • 3.0.1 - 2020-06-27
from @types/puppeteer GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

pull bot pushed a commit that referenced this pull request Aug 25, 2021
Previous attempt commit 3e919da
failed because the API surface was changed by a different commit
(53b1652) at the same time.

Bug: n/a
Test: n/a
Relnote: n/a
Change-Id: I9c3d0ffc5d3a78cf8a7f0514e358bb5c587b2f67
pull bot pushed a commit that referenced this pull request Aug 25, 2021
pull bot pushed a commit that referenced this pull request Sep 24, 2021
While in many cases query parameters are in the
form of myarg={myarg}, this should never be a hard
requirement. Instead, only the value within braces
(what is actually used as the argument name) should
be used when validating that all required
arguments are present in the NavDeepLink.

Relnote: "Fixed a regression introduced in
[Navigation `2.4.0-alpha09`](#2.4.0-alpha09) when using
deep links with query parameters where Navigation would
incorrectly validate argument names using the query
parameter name (i.e., the `id` of `?id={userId}`) rather
than using the actual argument names present in the value
(the `userId` in the example above)."
Test: new NavDestinationAndroidTest tests pass
BUG: 200845660

Change-Id: Id2f399a5e19e593f34e02fc811f1cc28ec0689b8
pull bot pushed a commit that referenced this pull request Feb 14, 2022
Now with toml fixes!

Test: ./gradlew bOS --dry-run
Change-Id: I888372d181532ff55cf51475bf04ab039be2c773
pull bot pushed a commit that referenced this pull request Feb 14, 2022
pull bot pushed a commit that referenced this pull request Feb 14, 2022
This reverts commit d25c04a.

Reason for revert: b/216514062; breaks local runs on osx

Change-Id: Iab86601df3f7603c10a90e235d0b3239ca5ae452
pull bot pushed a commit that referenced this pull request Feb 14, 2022
pull bot pushed a commit that referenced this pull request Jul 15, 2025
This CL adds the refresh() for SDKs where the refresh system API
is unavailable, ensuring the underlying window is always valid and
updated when accessed. This is important for preventing stale window
accesss and reducing test flakes often caused by window closures or
updates during testing.

Design: go/uiautomator-window-design
Bug: 425372420
Test: ./gradlew :test:uiautomator:i:t:connectedAndroidTest (UiWindowTest)
Relnote: New APIs for desktop multi-window
Merged-In: I40528316751814034580696f01ab78eb696e83bf
Change-Id: I40528316751814034580696f01ab78eb696e83bf
pull bot pushed a commit that referenced this pull request Aug 22, 2025
Turns out inspection-testing is not building snapshots, so we need to
keep it, instead swap just inspection:inspection

Test: None
Change-Id: Idd9d11fe21d3f915494eaf5ee1fb2afd7387f389
pull bot pushed a commit that referenced this pull request Aug 22, 2025
pull bot pushed a commit that referenced this pull request Sep 19, 2025
Deciding TalkBack whether it should intercept RSB movtion events to
navigate a11y focus is based on the input focus. If the scrollable node
fail to acquire input focus, TalkBack would treat it that RSB motion
events could be used by the input focused node and then it doesn't
intercept RSB movetion events.

Therefore, if we want to navigate a11y focus by RSB, we need to request
input focus to the scrollable node which has CollectionInfo.

Node #1 at (l=0.0, t=0.0, r=119.0, b=456.0)px
 |-Node #2 at (l=0.0, t=0.0, r=119.0, b=456.0)px, Tag: 'scalingLazyColumn'
    |-Node #4 at (l=0.0, t=-22.0, r=119.0, b=478.0)px
      CollectionInfo = 'androidx.compose.ui.semantics.CollectionInfo@8d7827'
      Focused = 'true'
      ...

Bug: b/445332360
Test: Run wear.compose.integration-tests.demos
Change-Id: I6be3cd527a60eb95679889e4c86e8240530894b0
pull bot pushed a commit that referenced this pull request Nov 4, 2025
When re-filling the cache window we were using old data, so we sometimes avoided re-caching items that have changed. When the dataset has changed and we need to re-fill the window, we need to clean-up the cached information (prefetched and item sizes) so the algorithm for prefetching will run for all new items. We're also now using the fact that there was a change in the visible item's keys to indicate the need to refill the window.

Test: Updated existing test.
Fixes: 454439658
Change-Id: I716ec2adbb230d6292743034e1ea1a2d9d36a766
pull bot pushed a commit that referenced this pull request Nov 4, 2025
pull bot pushed a commit that referenced this pull request Nov 7, 2025
This reverts commit fdc614d.

Reason for revert: broke g3

Change-Id: I932d0f0d2ff42cb8ae7342a3d3d65ada1891681d
pull bot pushed a commit that referenced this pull request Nov 7, 2025
pull bot pushed a commit that referenced this pull request Nov 20, 2025
When re-filling the cache window we were using old data, so we sometimes avoided re-caching items that have changed. When the dataset has changed and we need to re-fill the window, we need to clean-up the cached information (prefetched and item sizes) so the algorithm for prefetching will run for all new items. We're also now using the fact that there was a change in the visible item's keys to indicate the need to refill the window.

Test: Updated existing test.
Fixes: 454439658
Relnote: Introduce isCacheWindowRefillFixEnabled to control the roll out of the cache window refill fix.

Change-Id: I4e52baefd57b178834444a60cf43a016ec193e52
pull bot pushed a commit that referenced this pull request Nov 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants