Bump the major group across 1 directory with 7 updates

[dependabot]

Bumps the major group with 7 updates in the / directory:

Package	From	To
async-nats	0.46.0	0.47.0
sentry	0.47.0	0.48.0
sentry-tracing	0.47.0	0.48.0
lru	0.16.3	0.18.0
sha2	0.10.9	0.11.0
scraper	0.25.0	0.26.0
shapefile	0.7.0	0.8.0

Updates async-nats from 0.46.0 to 0.47.0

Release notes

Sourced from async-nats's releases.

async-nats/v0.47.0

This release adds subject validation (with opt-out possibility) and wraps while connect attempt in timeout, making it more robust.

Added

• Add Subject Validation by @​Jarema in nats-io/nats.rs#1525
• Add respond_with_headers method to handle responses with custom headers by @​giddyos in nats-io/nats.rs#1554
• Add local_address option to bind client to a specific local IP by @​wallyqs in nats-io/nats.rs#1539
• Implement Clone for ConnectOptions by @​MattPatchava in nats-io/nats.rs#1552

Fixed

• Fix invalid consumer rate limit json by @​Totodore in nats-io/nats.rs#1536
• Return error instead of panic when reply subject is empty by @​liamkinne in nats-io/nats.rs#1514
• Use proper doc comments by @​Xaeroxe in nats-io/nats.rs#1543
• Fix connection_timeout to cover full NATS handshake by @​rahsonaw in nats-io/nats.rs#1544

Changed

• Update rustls-native-certs from 0.7 to 0.8 by @​FreeMasen in nats-io/nats.rs#1507
• Remove once_cell and use std::sync::LazyLock instead by @​Jarema in nats-io/nats.rs#1534
• Bump bytes crate by @​Jarema in nats-io/nats.rs#1540
• Bump msrv by @​Jarema in nats-io/nats.rs#1509
• Update rustls-webpki to 0.103.10 by @​JohnMoon-Voyager in nats-io/nats.rs#1550
• Update dictionary by @​Jarema in nats-io/nats.rs#1556

New Contributors

• @​FreeMasen made their first contribution in nats-io/nats.rs#1507
• @​Xaeroxe made their first contribution in nats-io/nats.rs#1543
• @​MattPatchava made their first contribution in nats-io/nats.rs#1552
• @​JohnMoon-Voyager made their first contribution in nats-io/nats.rs#1550
• @​giddyos made their first contribution in nats-io/nats.rs#1554
• @​rahsonaw made their first contribution in nats-io/nats.rs#1544

Full Changelog: nats-io/nats.rs@async-nats/v0.46.0...async-nats/v0.47.0

Commits

• 0b4ca5e Release async-nats/v0.47.0
• e96ec26 Fix connection_timeout to cover full NATS handshake
• 5bd0810 Update dictionary
• c497c39 Add respond_with_headers method to handle responses with custom headers
• f7dcce2 Update rustls-webpki to 0.103.10
• d595b62 Implement Clone for ConnectOptions
• d239ec9 Add sync client deprecation version as 0.26
• b5e31f1 Deprecate old synchronous client
• 2f42dfb Add Subject & Header Validation
• c51d71c Improve doc comments
• Additional commits viewable in compare view

Updates sentry from 0.47.0 to 0.48.0

Release notes

Sourced from sentry's releases.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.

Changelog

Sourced from sentry's changelog.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

... (truncated)

Commits

• 7f8bb3f release: 0.48.0
• 352cfb8 build(deps): bump actix-http from 3.12.0 to 3.12.1 (#1075)
• 9a1373a build(deps): bump rustls-webpki from 0.103.10 to 0.103.13 (#1085)
• 1bcbbe6 build(deps): bump openssl from 0.10.75 to 0.10.78 (#1078)
• a41084f meta(changelog): Add changelog entries for Metrics PRs
• 3d57614 feat: Metrics feature
• afc5b71 feat(metrics): Add trace_metric transport rate limiting (#1066)
• a68455f feat!(metrics): Add before_send_metric callback (#1064)
• 3c4abb6 feat(metrics): Add metric user attributes from scope (#1063)
• 0e46166 feat(metrics): Attach default SDK attributes to metrics (#1062)
• Additional commits viewable in compare view

Updates sentry-tracing from 0.47.0 to 0.48.0

Release notes

Sourced from sentry-tracing's releases.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.

Changelog

Sourced from sentry-tracing's changelog.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

... (truncated)

Commits

• 7f8bb3f release: 0.48.0
• 352cfb8 build(deps): bump actix-http from 3.12.0 to 3.12.1 (#1075)
• 9a1373a build(deps): bump rustls-webpki from 0.103.10 to 0.103.13 (#1085)
• 1bcbbe6 build(deps): bump openssl from 0.10.75 to 0.10.78 (#1078)
• a41084f meta(changelog): Add changelog entries for Metrics PRs
• 3d57614 feat: Metrics feature
• afc5b71 feat(metrics): Add trace_metric transport rate limiting (#1066)
• a68455f feat!(metrics): Add before_send_metric callback (#1064)
• 3c4abb6 feat(metrics): Add metric user attributes from scope (#1063)
• 0e46166 feat(metrics): Attach default SDK attributes to metrics (#1062)
• Additional commits viewable in compare view

Updates lru from 0.16.3 to 0.18.0

Changelog

Sourced from lru's changelog.

v0.18.0 - 2026-04-27

• Fix unconstrained lifetime in get_or_insert_mut_ref.

v0.17.0 - 2026-04-14

• Upgrade hashbrown to 0.17.0 and update MSRV to 1.85.0.

v0.16.4 - 2026-04-13

• Add get_or_insert_with_key and variants.

Commits

• dac07e3 Merge pull request #234 from jeromefroe/jerome/prepare-0-18-0-release
• 0335315 Prepare 0.18.0 release
• e40bbdc Merge pull request #233 from paolobarbolini/get_or_insert_mut_ref-unconstrain...
• a615a5b Fix unconstrained lifetime in LruCache::get_or_insert_mut_ref
• 13321a9 Merge pull request #232 from jeromefroe/jerome/prepare-0-17-0-release
• f7d0ece Prepare 0.17.0 release
• 2d3d6d5 Merge pull request #231 from xtqqczze/deps/hashbrown
• 346e2fe Bump hashbrown to 0.17.0
• 1302b4e Update MSRV to 1.85.0
• d8c7f5c Merge pull request #230 from jeromefroe/jerome/prepare-0-16-4-release
• Additional commits viewable in compare view

Updates sha2 from 0.10.9 to 0.11.0

Commits

• ffe0939 Release sha2 0.11.0 (#806)
• 8991b65 Use the standard order of the [package] section fields (#807)
• 3d2bc57 sha2: refactor backends (#802)
• faa55fb sha3: bump keccak to v0.2 (#803)
• d3e6489 sha3 v0.11.0-rc.9 (#801)
• bbf6f51 sha2: tweak backend docs (#800)
• 155dbbf sha3: add default value for the DS generic parameter on TurboShake128/256...
• ed514f2 Use published version of keccak v0.2 (#799)
• 702bcd8 Migrate to closure-based keccak (#796)
• 827c043 sha3 v0.11.0-rc.8 (#794)
• Additional commits viewable in compare view

Updates scraper from 0.25.0 to 0.26.0

Release notes

Sourced from scraper's releases.

v0.26.0

What's Changed

• fix dom manipulation example by @​JayceFayne in rust-scraper/scraper#292
• Bump selectors from 0.33.0 to 0.35.0 by @​dependabot[bot] in rust-scraper/scraper#298
• Bump indexmap from 2.12.1 to 2.13.0 by @​dependabot[bot] in rust-scraper/scraper#294
• Upgrade ego-tree to 0.11.0 and html5ever to 0.37.1 by @​cfvescovo in rust-scraper/scraper#300
• Bump html5ever from 0.37.1 to 0.38.0 by @​mohe2015 in rust-scraper/scraper#303
• Bump selectors from 0.35.0 to 0.36.0 by @​dependabot[bot] in rust-scraper/scraper#307
• Bump html5ever from 0.38.0 to 0.39.0 by @​dependabot[bot] in rust-scraper/scraper#308
• Version 0.26.0 by @​adamreichold in rust-scraper/scraper#306

New Contributors

• @​JayceFayne made their first contribution in rust-scraper/scraper#292

Full Changelog: rust-scraper/scraper@v0.25.0...v0.26.0

Commits

• 170cdd3 Merge pull request #306 from rust-scraper/bump
• bca1839 Bump html5ever from 0.38.0 to 0.39.0
• d07444e Bump selectors from 0.35.0 to 0.36.0 (#307)
• 637a8d3 Version 0.26.0
• f3132d9 Bump html5ever from 0.37.1 to 0.38.0
• ff2ea51 cargo fmt
• 7d14577 Edition 2024
• 60cd9e7 Merge pull request #300 from rust-scraper/upgrade-ego-tree-html5ever
• ba8f3fc Upgrade ego-tree to 0.11.0 and html5ever to 0.37.1
• a2cfbe4 Bump indexmap from 2.12.1 to 2.13.0
• Additional commits viewable in compare view

Updates shapefile from 0.7.0 to 0.8.0

Changelog

Sourced from shapefile's changelog.

0.8.0

• Added serde feature which is forwarded to dbase, enabling serde support for dbase record field types.
• Added reading of .cpg files to detect the encoding of .dbf files.
• Fixed overly strict size-checks for shapes; shapes with a record size larger than expected are now read successfully (extra bytes are skipped) instead of returning an error.
• Updated geo-traits dependency to 0.3.
• Added Polygon::try_into_geo_traits(), which converts a polygon to an object that implements geo_traits::PolygonTrait.
• Converting to geo_types::Polygon is now fallible (i.e. TryFrom, not From).

Commits

• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.