Update dependency upgrades - non-major

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@react-navigation/native (source)	6.1.8 -> 6.1.9
@react-navigation/native-stack (source)	6.9.14 -> 6.9.15
detox	20.13.0 -> 20.13.1

---

Release Notes

react-navigation/react-navigation (@​react-navigation/native)

v6.1.9

Compare Source

Bug Fixes

• bump use-latest-callback to fix callback assignements (bc30315) - by @​satya164

wix/Detox (detox)

v20.13.1

Compare Source

What's Changed

Android

• 💥 "Android API 32, 33 (v12): .tap() acts like tap+hold" (#​3762) by @​ericschaal via #​4216

  ⬆️ This fixes an issue with Detox taps mistakenly registered as tap+hold on newer Android API levels (32+).
  Note: While the tapping issue might be resolved with the patch, there's a known issue with scrolling not working as intended on the new Android API. We're looking for the contributors.

• ⚙️ "Something is odd about runScriptWithArgs signature" (#​4127) by @​noomorph via #​4221

  Technically, this fix is a breaking change – it removes the runScriptWithArgs API, but since it never has worked, this should not be an issue. Now, you can use runScript to pass your arguments to the web elements and also get results (provided your function is synchronous):

  const isDisabled = await myWebButton.runScript(btn => btn.disabled);
  await myWebButton.runScript((btn, text) => { btn.textContent = text }, ['New text']);

iOS

• Preserve logs after device.resetContentAndSettings() by @​noomorph via #​4215

  Fixes a rare condition where the artifacts manager breaks down in the subsequent test after using device.resetContentAndSettings() in the previous one.

New Contributors

Thanks, @​ericschaal, for your first (and very valuable! 🏆 ) contribution in https://github.com/wix/Detox/pull/4216

Thanks, @​IrbisKronos, for your second contribution this year, the new social networks ribbon on the website.

Thanks, @​monholm, for a tip on how to list available device specs.

Full Changelog: wix/Detox@20.13.0...20.13.1

---

Configuration

📅 Schedule: Branch creation - "after 4pm on thursday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[socket-security]

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
detox	20.13.1	filesystem, shell, environment	+40	14.7 MB	wix.mobile
@react-navigation/native	6.1.8...6.1.9	None	+2/-2	1.16 MB
@react-navigation/native-stack	6.9.14...6.9.15	None	+4/-4	1.61 MB

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Native code	dtrace-provider	0.8.8	Location: binding.gyp +1 more instances...	detox@20.13.1 via package.json

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore dtrace-provider@0.8.8