Skip to content

build(deps): bump chromiumoxide from 0.7.0 to 0.8.0 - #23

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/chromiumoxide-0.8.0
Open

build(deps): bump chromiumoxide from 0.7.0 to 0.8.0#23
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/chromiumoxide-0.8.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 8, 2026

Copy link
Copy Markdown

Bumps chromiumoxide from 0.7.0 to 0.8.0.

Release notes

Sourced from chromiumoxide's releases.

v0.8.0

What's Changed

See CHANGELOG

New Contributors

Full Changelog: mattsse/chromiumoxide@v0.7.0...v0.8.0

Changelog

Sourced from chromiumoxide's changelog.

[0.8.0] 2025-11-28

Breaking Changes

Due to the support of new browsers in the fetcher, we changed the API. The changes are mainly related to how you can request a specific version of the browser. Previously you could only request a chromium revision, now we support chrome versions, channel and milestone.

BrowserFetcherOptions::builder()
  .with_kind(BrowserKind::Chrome)
  .with_version(BrowserVersion::Channel(Channel::Beta))
  .build()

We also change the output format of the fetch. It is now called a BrowserFetcherInstallation and contains a BuildInfo. We garantee that at least the version or revision will be present in that struct, but not always both.

let installation = chromiumoxide_fetcher::BrowserFetcher::new(options).fetch().await?;
println!("Executable path: {}", installation.executable_path.display());

Finally, we switched the async runtime tokio by default. We will remove for support for async-std in the next release. If you want to part of the discussion on other runtime support, see #273.

Changed

  • Bumped MSRV to 1.85 to support edition 2024
  • Update async-tungstenite to 0.32.0
  • Update which to 8.0.0
  • Replace winreg by windows-registry
  • Updated PDL to r1519099 (Chromium 142.0.7431.0)
  • Updated fetcher to r1520176 (Chromium 142.0.7435.0)
  • Fetch now supports Chrome for testing and Chrome Headless Shell
  • Now uses tokio by default

Added

  • Add option to disable automation detection
  • Expose the cmd module for access to CommandChain

Fixed

  • Fixed typo in feature _fetcher-rustls-tokio
  • More resilient message parsing, it should now not crash on unknown events coming from the browser
  • Extensions should only be disabled when no extensions are provided
Commits

@dependabot @github

dependabot Bot commented on behalf of github Jul 8, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Bumps [chromiumoxide](https://github.com/mattsse/chromiumoxide) from 0.7.0 to 0.8.0.
- [Release notes](https://github.com/mattsse/chromiumoxide/releases)
- [Changelog](https://github.com/mattsse/chromiumoxide/blob/main/CHANGELOG.md)
- [Commits](mattsse/chromiumoxide@chromiumoxide_cdp-v0.7.0...v0.8.0)

---
updated-dependencies:
- dependency-name: chromiumoxide
  dependency-version: 0.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/chromiumoxide-0.8.0 branch from 7098cd2 to ea5f6ca Compare July 11, 2026 11:12
@dependabot @github

dependabot Bot commented on behalf of github Jul 24, 2026

Copy link
Copy Markdown
Author

Dependabot can't resolve your Rust dependency files. Because of this, Dependabot cannot update this pull request.

1 similar comment
@dependabot @github

dependabot Bot commented on behalf of github Jul 28, 2026

Copy link
Copy Markdown
Author

Dependabot can't resolve your Rust dependency files. Because of this, Dependabot cannot update this pull request.

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.

0 participants