chore(deps): bump @appium/logger from 2.0.12 to 3.0.0-beta.0

[dependabot]

Bumps @appium/logger from 2.0.12 to 3.0.0-beta.0.

Release notes

Sourced from @​appium/logger's releases.

@​appium/logger@​3.0.0-beta.0

3.0.0-beta.0 (2026-09-19)

⚠ BREAKING CHANGES

• support: Any script or tool that consumes Appium CLI output (driver/plugin list/install/update, doctor, etc.) and relies on the previous stream layout will need to be updated. Previously, non-JSON human-readable output (info/success/warning messages) was written to STDERR, with STDOUT reserved almost exclusively for --json output. Now that output goes to STDOUT, and only actual errors go to STDERR.
• support: Scripts that discarded STDOUT (1>/dev/null) to suppress "chatter" while relying on STDERR for status text will now see that text on STDOUT instead.
• support: Scripts that captured STDERR to detect/log informational or success messages will no longer see them there — only genuine errors will appear on STDERR. --json output and error behavior are unaffected: --json continues to write clean JSON to STDOUT only, and errors continue to go to STDERR.
• support: @​appium/logger's Log class changes its default output stream from STDERR to STDOUT for all levels except error, and adds an errorStream/stderrLevel pair of properties. Any code that set .stream on a Log instance expecting it to capture all levels (including error) will now need to also set .errorStream to the same target.
• logger: @​appium/logger and @​appium/support no longer export a default log — import the named log export instead.
• logger: AppiumLogger#errorAndThrow has been removed; use errorWithException instead.
• logger: Logger#enableProgress, disableProgress, progressEnabled, enableUnicode, disableUnicode have been removed; they were already permanently disabled no-ops.
• the minimum supported Node.js engine is set to ^22.22.2 || ^24.15.0 || >=26.0.0
• require('@​appium/support') no longer works; consumers must import it instead.
• require('@​appium/base-driver') no longer works; drivers extending BaseDriver via require must switch to import.
• require('@​appium/base-plugin') no longer works; plugins extending BasePlugin via require must switch to import.
• require('appium') no longer works; plugins extending the package via require must switch to import.
• require('@​appium/fake-plugin') no longer works; consumers must import it instead.
• require('@​appium/fake-driver') no longer works; consumers must import it instead.
• require('@​appium/types') no longer works; consumers must import it instead.
• require('@​appium/logger') no longer works; consumers must import it instead.
• require('@​appium/schema') no longer works; consumers must import it instead.

Features

• bump minimum supported Node.js engine to ^22.22.2 || ^24.15.0 || >=26.0.0 (#22685) (9f4a11e)
• convert remaining monorepo packages to ESM-only (#22674) (3516e50)

Bug Fixes

• support: route non-error CLI console output to stdout (#22742) (4eb4d7f)

Code Refactoring

• logger: remove default exports and dead logging APIs (#22719) (fe24f52)

Changelog

Sourced from @​appium/logger's changelog.

3.0.0-beta.0 (2026-09-19)

⚠ BREAKING CHANGES

• support: Any script or tool that consumes Appium CLI output (driver/plugin list/install/update, doctor, etc.) and relies on the previous stream layout will need to be updated. Previously, non-JSON human-readable output (info/success/warning messages) was written to STDERR, with STDOUT reserved almost exclusively for --json output. Now that output goes to STDOUT, and only actual errors go to STDERR.
• support: Scripts that discarded STDOUT (1>/dev/null) to suppress "chatter" while relying on STDERR for status text will now see that text on STDOUT instead.
• support: Scripts that captured STDERR to detect/log informational or success messages will no longer see them there — only genuine errors will appear on STDERR. --json output and error behavior are unaffected: --json continues to write clean JSON to STDOUT only, and errors continue to go to STDERR.
• support: @​appium/logger's Log class changes its default output stream from STDERR to STDOUT for all levels except error, and adds an errorStream/stderrLevel pair of properties. Any code that set .stream on a Log instance expecting it to capture all levels (including error) will now need to also set .errorStream to the same target.
• logger: @​appium/logger and @​appium/support no longer export a default log — import the named log export instead.
• logger: AppiumLogger#errorAndThrow has been removed; use errorWithException instead.
• logger: Logger#enableProgress, disableProgress, progressEnabled, enableUnicode, disableUnicode have been removed; they were already permanently disabled no-ops.
• the minimum supported Node.js engine is set to ^22.22.2 || ^24.15.0 || >=26.0.0
• require('@​appium/support') no longer works; consumers must import it instead.
• require('@​appium/base-driver') no longer works; drivers extending BaseDriver via require must switch to import.
• require('@​appium/base-plugin') no longer works; plugins extending BasePlugin via require must switch to import.
• require('appium') no longer works; plugins extending the package via require must switch to import.
• require('@​appium/fake-plugin') no longer works; consumers must import it instead.
• require('@​appium/fake-driver') no longer works; consumers must import it instead.
• require('@​appium/types') no longer works; consumers must import it instead.
• require('@​appium/logger') no longer works; consumers must import it instead.
• require('@​appium/schema') no longer works; consumers must import it instead.

Features

• bump minimum supported Node.js engine to ^22.22.2 || ^24.15.0 || >=26.0.0 (#22685) (9f4a11e)
• convert remaining monorepo packages to ESM-only (#22674) (3516e50)

Bug Fixes

• support: route non-error CLI console output to stdout (#22742) (4eb4d7f)

Code Refactoring

• logger: remove default exports and dead logging APIs (#22719) (fe24f52)

2.0.11 (2026-08-24)

Bug Fixes

• logger: mask secure values surrounded by non-word characters (#22553) (8ac6bfc)

2.0.10 (2026-07-25)

Note: Version bump only for package @​appium/logger

... (truncated)

Commits

• e303649 chore: publish
• 4eb4d7f fix(support)!: route non-error CLI console output to stdout (#22742)
• fe24f52 refactor(logger)!: remove default exports and dead logging APIs (#22719)
• 9f4a11e feat!: bump minimum supported Node.js engine to ^22.22.2 || ^24.15.0 || >=26....
• 3516e50 feat!: convert remaining monorepo packages to ESM-only (#22674)
• See full diff 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.