Bump tar and @wdio/browserstack-service

[dependabot]

Bumps tar to 7.5.22 and updates ancestor dependency @wdio/browserstack-service. These dependencies need to be updated together.

Updates tar from 6.2.1 to 7.5.22

Changelog

Sourced from tar's changelog.

Changelog

7.5

• Added zstd compression support.
• Consistent TOCTOU behavior in sync t.list
• Only read from ustar block if not specified in Pax
• Fix sync tar.list when file size reduces while reading
• Sanitize absolute linkpaths properly
• Prevent writing hardlink entries to the archive ahead of their file target

7.4

• Deprecate onentry in favor of onReadEntry for clarity.

7.3

• Add onWriteEntry option

7.2

• DRY the command definitions into a single makeCommand method, and update the type signatures to more appropriately infer the return type from the options and arguments provided.

7.1

• Update minipass to v7.1.0
• Update the type definitions of write() and end() methods on Unpack and Parser classes to be compatible with the NodeJS.WritableStream type in the latest versions of @types/node.

7.0

• Drop support for node <18
• Rewrite in TypeScript, provide ESM and CommonJS hybrid interface
• Add tree-shake friendly exports, like import('tar/create') and import('tar/read-entry') to get individual functions or classes.
• Add chmod option that defaults to false, and deprecate noChmod. That is, reverse the default option regarding explicitly setting file system modes to match tar entry settings.
• Add processUmask option to avoid having to call process.umask() when chmod: true (or noChmod: false) is set.

... (truncated)

Commits

• 2a22bfc 7.5.22
• df1cd8d Allow transform to be falsey
• 0cd9cc3 7.5.21
• 631ae59 list: prevent unbounded recursion
• ebbb720 7.5.20
• 2f27196 fix: fully disable and dispose of unzip when aborting parser
• be440da 7.5.19
• 2812e93 add maxDecompressionRatio guard against explosive decompression
• 9ecd4d2 7.5.18
• 9e78bf0 refuse to let header size be less than 0
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by isaacs, a new releaser for tar since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

Updates @wdio/browserstack-service from 8.50.0 to 9.34.1

Release notes

Sourced from @​wdio/browserstack-service's releases.

@​wdio/browserstack-service@​9.34.1

Patch Changes

• b9bb4eb: - Fixed browserstack_executor commands issued through browser.execute() or browser.executeAsync() being ignored in WebDriver BiDi sessions.

@​wdio/browserstack-service@​9.34.0

Minor Changes

• aa16aa1: - The debug logs the service uploads at the end of a run now include a copy of your wdio.conf file (and the local config files it imports) plus your package.json, with values under known credential keys removed on a best-effort basis, so BrowserStack support can investigate configuration issues without asking you to reproduce them.
  • Set disableAutoCaptureLogs: true in the service options, or BROWSERSTACK_DISABLE_AUTO_CAPTURE_LOGS=true, to turn this upload off entirely.

Patch Changes

• 69ede2a: - Fixed inflated build durations on the Test Observability dashboard for WebdriverIO + Cucumber runs: hooks interrupted mid-run are now closed instead of staying "in progress" until the hook timeout.
• f75b180: - Fixed WebdriverIO (Mocha) builds occasionally being reported as timed out even though the test run finished successfully.
• 0986e13: - Fixed App Automate and Automate session names staying on the static sessionName capability instead of the test title, for suites that reload the session between tests or whose run ends before the WebdriverIO after hook.
• 941b677: - Made the Test Reporting build-completion signal more resilient on restricted corporate networks, so builds are less likely to be left showing as "running" after a run ends.
  • Each delivery attempt is now individually time-bounded, so a hung connection can no longer stall the end of a run.
  • When the signal still cannot be delivered, the log now records the underlying network reason (for example a DNS or proxy failure) instead of a generic fetch failed.
• 52f0cf4: - Fixed test results not appearing in Test Reporting for WebdriverIO + Mocha when the project is not a git repository.
  • Fixed the BrowserStack binary not updating once a copy was already present, which could leave a machine on an old binary indefinitely.

@​wdio/browserstack-service@​9.33.2

Patch Changes

• b688f05: - Fixed Accessibility Automation producing no report for WebdriverIO suites running on the jasmine framework. Accessibility scans now run for jasmine specs, as they already did for mocha.

@​wdio/browserstack-service@​9.33.1

Patch Changes

• 4b19d7a: - Fixed App Automate session names not updating to the test title when the app is provided via the appium:app capability.
• 929b1f5: - Fixed WebdriverIO test results sometimes not appearing (builds staying "in progress") when the build-completion signal failed or the test runner was interrupted.

@​wdio/browserstack-service@​9.33.0

Minor Changes

• e99828d: - Fixed SDK logs not being uploaded when a test run is interrupted (Ctrl-C or CI job cancellation); interrupted runs are now correctly reported with their termination reason.

Patch Changes

• 74c2682: - Read the apis service-URL map from the binary's new config.sessionData bucket (SDK-6821 session.config split), with the flat config.apis as backward-compat fallback. Single-point change in setConfig; verified npm run build clean and the vitest suite shows zero new failures vs main (68 pre-existing environmental failures identical on both).

@​wdio/browserstack-service@​9.32.1

Patch Changes

• aefd604: - Fixed a statically-skipped test (it.skip) being left orphaned as "in progress" on the Test Observability dashboard in the CLI flow. Such tests are reported from the un-awaited onTestSkip reporter hook, so their TestRunFinished event could still be pending when the worker tore down; the after() hook now drains these skip reports before the session closes so the test is correctly reported as skipped.
• 1a973e9: - fix: Accessibility command wrapping.
• a24973b: - Fixed Test Observability not being fully disabled for a run when the build could not be started (e.g. an unsupported framework) — such sessions no longer emit observability events or get linked to a non-existent build.
• 8539e5f: fix(a11y): restore per-command auto-scanning for App Automate accessibility sessions

... (truncated)

Changelog

Sourced from @​wdio/browserstack-service's changelog.

9.34.1

Patch Changes

• b9bb4eb: - Fixed browserstack_executor commands issued through browser.execute() or browser.executeAsync() being ignored in WebDriver BiDi sessions.

9.34.0

Minor Changes

• aa16aa1: - The debug logs the service uploads at the end of a run now include a copy of your wdio.conf file (and the local config files it imports) plus your package.json, with values under known credential keys removed on a best-effort basis, so BrowserStack support can investigate configuration issues without asking you to reproduce them.
  • Set disableAutoCaptureLogs: true in the service options, or BROWSERSTACK_DISABLE_AUTO_CAPTURE_LOGS=true, to turn this upload off entirely.

Patch Changes

• 69ede2a: - Fixed inflated build durations on the Test Observability dashboard for WebdriverIO + Cucumber runs: hooks interrupted mid-run are now closed instead of staying "in progress" until the hook timeout.
• f75b180: - Fixed WebdriverIO (Mocha) builds occasionally being reported as timed out even though the test run finished successfully.
• 0986e13: - Fixed App Automate and Automate session names staying on the static sessionName capability instead of the test title, for suites that reload the session between tests or whose run ends before the WebdriverIO after hook.
• 941b677: - Made the Test Reporting build-completion signal more resilient on restricted corporate networks, so builds are less likely to be left showing as "running" after a run ends.
  • Each delivery attempt is now individually time-bounded, so a hung connection can no longer stall the end of a run.
  • When the signal still cannot be delivered, the log now records the underlying network reason (for example a DNS or proxy failure) instead of a generic fetch failed.
• 52f0cf4: - Fixed test results not appearing in Test Reporting for WebdriverIO + Mocha when the project is not a git repository.
  • Fixed the BrowserStack binary not updating once a copy was already present, which could leave a machine on an old binary indefinitely.

9.33.2

Patch Changes

• b688f05: - Fixed Accessibility Automation producing no report for WebdriverIO suites running on the jasmine framework. Accessibility scans now run for jasmine specs, as they already did for mocha.

9.33.1

Patch Changes

• 4b19d7a: - Fixed App Automate session names not updating to the test title when the app is provided via the appium:app capability.
• 929b1f5: - Fixed WebdriverIO test results sometimes not appearing (builds staying "in progress") when the build-completion signal failed or the test runner was interrupted.

9.33.0

Minor Changes

• e99828d: - Fixed SDK logs not being uploaded when a test run is interrupted (Ctrl-C or CI job cancellation); interrupted runs are now correctly reported with their termination reason.

Patch Changes

• 74c2682: - Read the apis service-URL map from the binary's new config.sessionData bucket (SDK-6821 session.config split), with the flat config.apis as backward-compat fallback. Single-point change in setConfig; verified npm run build clean and the vitest suite shows zero new failures vs main (68 pre-existing environmental failures identical on both).

9.32.1

Patch Changes

... (truncated)

Commits

• de9518d Version Packages
• dc7fe43 Merge branch 'main' into bidi-browserstack-executor-http
• b6f1f18 fix(browserstack-service): route executeAsync executor payloads over HTTP on ...
• d9c585c fix(browserstack-service): gate BiDi executor routing on BrowserStack sessions
• c1ebb00 fix(browserstack-service): tolerate leading whitespace in BiDi executor routing
• da8f719 Version Packages
• d4878ad Merge pull request #148 from browserstack/fix/sdk-7270-session-name-per-test
• ba6a493 Merge pull request #147 from browserstack/feat/sdk-7250-capture-wdio-conf
• fb9a578 Merge pull request #145 from browserstack/fix/sdk-7233-wdio-test-file-path-an...
• 3eeb3e5 Merge pull request #143 from browserstack/fix/sdk-7229-buildstop-resilience
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}