Sourced from reqwest's releases.

v0.12.18

What's Changed

• Fix compilation when socks enabled without TLS.

v0.12.17

What's Changed

• build: Fix compilation issues on macOS by @​0x676e67 in seanmonstar/reqwest#2696

v0.12.16

Highlights

• Add ClientBuilder::http3_congestion_bbr() to enable BBR congestion control.
• Add ClientBuilder::http3_send_grease() to configure whether to send use QUIC grease.
• Add ClientBuilder::http3_max_field_section_size() to configure the maximum response headers.
• Add ClientBuilder::tcp_keepalive_interval() to configure TCP probe interval.
• Add ClientBuilder::tcp_keepalive_retries() to configure TCP probe count.
• Add Proxy::headers() to add extra headers that should be sent to a proxy.
• Fix redirect::Policy::limit() which had an off-by-1 error, allowing 1 more redirect than specified.
• Fix HTTP/3 to support streaming request bodies.
• (wasm) Fix null bodies when calling Response::bytes_stream().

What's Changed

• Clarify that Response::content_length() is not derived from a Content-Length header in docs by @​babolivier in seanmonstar/reqwest#2588
• docs: link to char::REPLACEMENT_CHARACTER by @​marcospb19 in seanmonstar/reqwest#1880
• feat: add H3 client config support by @​smalls0098 in seanmonstar/reqwest#2609
• chore: update brotli to v7 by @​nyurik in seanmonstar/reqwest#2620
• Do not pull in an entirely different DEFLATE implementation just for tests by @​Shnatsel in seanmonstar/reqwest#2625
• chore: fix some typos in comment by @​xixishidibei in seanmonstar/reqwest#2628
• fix(wasm): handle null body in bytes_stream by @​alongubkin in seanmonstar/reqwest#2632
• ClientBuilder::interface on macOS/Solarish OSes by @​hawkw in seanmonstar/reqwest#2623
• ci: use ubuntu-latest in nightly job by @​seanmonstar in seanmonstar/reqwest#2646
• feat: BBR congestion control for http3 by @​threeninesixseven in seanmonstar/reqwest#2642
• feat: Add extentions for Request by @​Xuanwo in seanmonstar/reqwest#2647
• refactor: Store request timeout in request extensions instead by @​Xuanwo in seanmonstar/reqwest#2650
• chore: make ci pass by @​linyihai in seanmonstar/reqwest#2666
• update h3 dependencys by @​Ruben2424 in seanmonstar/reqwest#2670
• Document reqwest can make TLS and cookie requests with Wasm by @​nickbabcock in seanmonstar/reqwest#2661
• fix(redirect): make the number of redirects of policy matches its maximum limit. by @​linyihai in seanmonstar/reqwest#2664
• Exposed hyper tcp keepalive interval and retries parameters by @​mackliet in seanmonstar/reqwest#2675
• refactor: use hyper-util's proxy::Matcher by @​seanmonstar in seanmonstar/reqwest#2681
• Support streaming request body in HTTP/3 by @​ducaale in seanmonstar/reqwest#2673
• refactor: use hyper-util Tunnel by @​seanmonstar in seanmonstar/reqwest#2684
• Upgrade webpki-roots to 1 by @​djc in seanmonstar/reqwest#2688
• refactor: remove futures-util unless using stream/multipart/compression/blocking by @​paolobarbolini in seanmonstar/reqwest#2692
• chore: replace rustls-pemfile with rustls-pki-types by @​tottoto in seanmonstar/reqwest#2541
• Ensure H3ResponseFuture Implements Sync by @​ducaale in seanmonstar/reqwest#2685
• feat(redirect): Using FollowRedirect from tower-http to handle the redirect loop by @​linyihai in seanmonstar/reqwest#2617
• feat: add customizable headers in proxy mode by @​chanbengz in seanmonstar/reqwest#2600

... (truncated)

Sourced from reqwest's changelog.

v0.12.18

• Fix compilation when socks enabled without TLS.

v0.12.17

• Fix compilation on macOS.

v0.12.16

• Add ClientBuilder::http3_congestion_bbr() to enable BBR congestion control.
• Add ClientBuilder::http3_send_grease() to configure whether to send use QUIC grease.
• Add ClientBuilder::http3_max_field_section_size() to configure the maximum response headers.
• Add ClientBuilder::tcp_keepalive_interval() to configure TCP probe interval.
• Add ClientBuilder::tcp_keepalive_retries() to configure TCP probe count.
• Add Proxy::headers() to add extra headers that should be sent to a proxy.
• Fix redirect::Policy::limit() which had an off-by-1 error, allowing 1 more redirect than specified.
• Fix HTTP/3 to support streaming request bodies.
• (wasm) Fix null bodies when calling Response::bytes_stream().

• 595c80b v0.12.18
• f279ad1 fix compilation if socks is enabled without tls
• fed6bc6 ci: add a feature powerset check job
• 56ed35b v0.12.17
• f0bf46b build: Fix compilation issues on macOS (#2696)
• 99259cb v0.12.16
• 57670ac feat: add customizable headers for reqwest::Proxy (#2600)
• d9cf60e refactor: Using FollowRedirect from tower-http to handle the redirect l...
• 75f62f2 fix: ensure H3ResponseFuture is sync (#2685)
• 0e1d188 chore: replace rustls-pemfile with rustls-pki-types (#2541)
• Additional commits viewable in compare view

Sourced from uuid's releases.

v1.17.0

What's Changed

• Added convenience implementation TryFrom for std by @​Nahuel-M in uuid-rs/uuid#819
• Update OSX builds to arm by @​KodrAus in uuid-rs/uuid#825
• Replace derive(Hash) with manual impl in Uuid by @​diopoex in uuid-rs/uuid#824
• Add wasm32v1-none Support by @​bushrat011899 in uuid-rs/uuid#828
• Prepare for 1.17.0 release by @​KodrAus in uuid-rs/uuid#829

New Contributors

• @​Nahuel-M made their first contribution in uuid-rs/uuid#819
• @​diopoex made their first contribution in uuid-rs/uuid#824

Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.16.0...v1.17.0

• 2fd9b61 Merge pull request #829 from uuid-rs/cargo/v1.17.0
• ed0d385 prepare for 1.17.0 release
• c54cadc Merge pull request #828 from bushrat011899/wasm32v1-none
• 625d769 Fix typo in MVP Web CI
• 9d638e0 Add MVP Web CI Task
• 83dc528 Add wasm32v1-none support
• 5fbd843 Merge pull request #824 from diopoex/main
• 6635ae4 Merge pull request #825 from uuid-rs/ci/aarch64-apple-darwin
• b2370f2 update toolchain for outdated job
• c74ad33 update OSX builds to arm
• Additional commits viewable in compare view

Sourced from tokio's releases.

Tokio v1.45.1

1.45.1 (May 24th, 2025)

This fixes a regression on the wasm32-unknown-unknown target, where code that previously did not panic due to calls to Instant::now() started failing. This is due to the stabilization of the first time-based metric.

Fixed

• Disable time-based metrics on wasm32-unknown-unknown (#7322)

#7322: tokio-rs/tokio#7322

• 3768696 chore: prepare Tokio v1.45.1 (#7359)
• 421a7b0 rt: do not track time-based metrics on wasm32-unknown-unknown (#7322)
• b1bdb3c ci: update macros_type_mismatch for Rust 1.87.0 (#7339)
• See full diff in compare view

Sourced from clap's releases.

v4.5.39

[4.5.39] - 2025-05-27

Fixes

• (help) Show short flag aliases before long
• (help) Merge the short and long flag alias lists

Sourced from clap's changelog.

[4.5.39] - 2025-05-27

Fixes

• (help) Show short flag aliases before long
• (help) Merge the short and long flag alias lists

• ed2360f chore: Release
• 196a14b docs: Update changelog
• cd622ab Merge pull request #5846 from ribru17/alias_fn_dedup
• 48ff72b fix(complete): Deduplicate bash subcmd cases
• b1b6f17 Merge pull request #5843 from epage/link
• 5900216 fix(derive): Update link for derive attributes
• fde45f9 chore: Release
• 45d5d7e docs: Update changelog
• 4b82b97 chore: Release
• a982adf docs: Update changelog
• Additional commits viewable in compare view

• See full diff in compare view

Sourced from backon's releases.

v1.5.1

What's Changed

• docs: add wasm32 demo by @​XmchxUp in Xuanwo/backon#196
• fix no sleeper feature can't set sleeper in retry with context by @​Sherlock-Holo in Xuanwo/backon#199
• Bump to version 1.5.1 by @​Xuanwo in Xuanwo/backon#200

New Contributors

• @​Sherlock-Holo made their first contribution in Xuanwo/backon#199

Full Changelog: https://github.com/Xuanwo/backon/compare/v1.5.0...v1.5.1

• 2413c8f Bump to version 1.5.1 (#200)
• d1d3941 fix no sleeper feature can't set sleeper in retry with context (#199)
• 03a47d3 docs: add wasm32 demo (#196)
• See full diff in compare view

• See full diff in compare view

Sourced from opentelemetry_sdk's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

• c811cde chore: Prepare release 0.30.0 (#2999)
• 200885a fix: fix trace id in logs when using set_parent nested in a trace span (#2924)
• c24369e chore: Update metric sdk to stable status (#2996)
• bf22aeb fix: Remove pub fields and replace with getter method consistently across … (...
• 4be1a32 fix: remove cardinality capping via instrument advice (#2995)
• 3d04c16 docs: Add metric doc (#2946)
• 2018959 fix: Fix validation in Metric stream (#2991)
• 8c29ca7 chore: leverage fallback resolver for MSRV check (#2993)
• 4b3a383 chore: add required features to benches (#2990)
• ebbebf5 fix: Further trim public API on views (#2989)
• Additional commits viewable in compare view

Sourced from opentelemetry's releases.

0.30.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.30.0 for this release).

This release also upgrades Metrics-SDK to stable!

See summary of release notes: https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.30.md

Sourced from opentelemetry's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

• c811cde chore: Prepare release 0.30.0 (#2999)
• 200885a fix: fix trace id in logs when using set_parent nested in a trace span (#2924)
• c24369e chore: Update metric sdk to stable status (#2996)
• bf22aeb fix: Remove pub fields and replace with getter method consistently across … (...
• 4be1a32 fix: remove cardinality capping via instrument advice (#2995)
• 3d04c16 docs: Add metric doc (#2946)
• 2018959 fix: Fix validation in Metric stream (#2991)
• 8c29ca7 chore: leverage fallback resolver for MSRV check (#2993)
• 4b3a383 chore: add required features to benches (#2990)
• ebbebf5 fix: Further trim public API on views (#2989)
• Additional commits viewable in compare view

Sourced from opentelemetry-otlp's releases.

0.30.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.30.0 for this release).

This release also upgrades Metrics-SDK to stable!

See summary of release notes: https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.30.md

Sourced from opentelemetry-otlp's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

• c811cde chore: Prepare release 0.30.0 (#2999)
• 200885a fix: fix trace id in logs when using set_parent nested in a trace span (#2924)
• c24369e chore: Update metric sdk to stable status (#2996)
• bf22aeb fix: Remove pub fields and replace with getter method consistently across … (...
• 4be1a32 fix: remove cardinality capping via instrument advice (#2995)
• 3d04c16 docs: Add metric doc (#2946)
• 2018959 fix: Fix validation in Metric stream (#2991)
• 8c29ca7 chore: leverage fallback resolver for MSRV check (#2993)
• 4b3a383 chore: add required features to benches (#2990)
• ebbebf5 fix: Further trim public API on views (#2989)
• Additional commits viewable in compare view

Sourced from opentelemetry-semantic-conventions's releases.

0.30.0 Release

See changelog for individual crates to know the exact set of changes. All crates in this repo follows same version (0.30.0 for this release).

This release also upgrades Metrics-SDK to stable!

See summary of release notes: https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.30.md

Sourced from opentelemetry-semantic-conventions's changelog.

Release Notes 0.30

OpenTelemetry Rust 0.30 introduces a few breaking changes to the opentelemetry_sdk crate in the metrics feature. These changes were essential to drive the Metrics SDK towards stability. With this release, the Metrics SDK is officially declared stable. The Metrics API was declared stable last year, and previously, the Logs API, SDK, and OTel-Appender-Tracing were also marked stable. Importantly, no breaking changes have been introduced to components already marked as stable.

It is worth noting that the opentelemetry-otlp crate remains in a Release-Candidate state and is not yet considered stable. With the API and SDK for Logs and Metrics now stable, the focus will shift towards further refining and stabilizing the OTLP Exporters in upcoming releases. Additionally, Distributed Tracing is expected to progress towards stability, addressing key interoperability challenges.

For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.

Key Changes

Metrics SDK Improvements

1. Stabilized "view" features: Previously under an experimental feature flag, views can now be used to modify the name, unit, description, and cardinality limit of a metric. Advanced view capabilities, such as changing aggregation or dropping attributes, remain under the experimental feature flag.

2. Cardinality capping: Introduced the ability to cap cardinality and configure limits using views.

3. Polished public API: Refined the public API to hide implementation details from exporters, enabling future internal optimizations and ensuring consistency. Some APIs related to authoring custom metric readers have been moved behind experimental feature flags. These advanced use cases require more time to finalize the API surface before being included in the stable release.

Context-Based Suppression

Added the ability to suppress telemetry based on Context. This feature prevents telemetry-induced-telemetry scenarios and addresses a long-standing issue. Note that suppression relies on proper context propagation. Certain libraries used in OTLP Exporters utilize tracing but do not adopt OpenTelemetry's context propagation. As a result, not all telemetry is automatically suppressed with this feature. Improvements in this area are expected in future releases.

Next Release

... (truncated)

• c811cde chore: Prepare release 0.30.0 (#2999)
• 200885a fix: fix trace id in logs when using set_parent nested in a trace span (#2924)
• c24369e chore: Update metric sdk to stable status (#2996)
• bf22aeb fix: Remove pub fields and replace with getter method consistently across … (...
• 4be1a32 fix: remove cardinality capping via instrument advice (#2995)
• 3d04c16 docs: Add metric doc (#2946)
• 2018959 fix: Fix validation in Metric stream (#2991)
• 8c29ca7 chore: leverage fallback resolver for MSRV check (#2993)
• 4b3a383 chore: add required features to benches (#2990)
• ebbebf5 fix: Further trim public API on views (#2989)
• Additional commits viewable in compare view

• See full diff in compare view

Sourced from hyper-util's releases.

v0.1.13

tl;dr

• Fix HttpConnector to always prefer IPv6 addresses first, if happy eyeballs is enabled.
• Fix legacy::Client to return better errors if available on the connection.

What's Changed

• fix(client): prefer IPv6 addresses before IPv4 even if resolver ordered differently by @​seanmonstar in hyperium/hyper-util#194
• chore(test): make proxy test robust wrt IPv4/v6 by @​Fabian-Gruenbichler in hyperium/hyper-util#195
• refactor: limit dependency futures-util to tests and client-legacy by @​hanna-kruppe in hyperium/hyper-util#192
• Fix some clippy lints by @​jplatte in hyperium/hyper-util#196
• ConnectErrors improvements by @​seanmonstar in hyperium/hyper-util#197
• fix(client): race in connection errors propagation by @​dare3path in hyperium/hyper-util#184

New Contributors

• @​Fabian-Gruenbichler made their first contribution in hyperium/hyper-util#195
• @​hanna-kruppe made their first contribution in hyperium/hyper-util#192
• @​jplatte made their first contribution in hyperium/hyper-util#196
• @​dare3path made their first contribution in hyperium/hyper-util#184

Full Changelog: https://github.com/hyperium/hyper-util/compare/v0.1.12...v0.1.13

Sourced from hyper-util's changelog.

0.1.13 (2025-05-27)

• Fix HttpConnector to always prefer IPv6 addresses first, if happy eyeballs is enabled.
• Fix legacy::Client to return better errors if available on the connection.

• 2c3c55f v0.1.13
• a01e6b2 fix(client): improve client errors details if available (#184)
• fc1d699 refactor(client): add socket addr to ConnectError
• 0959d46 refactor(client): return the first connect error, not the last
• 6328823 refactor(client): don't allocate for ConnectError messages
• 3a971c9 Fix some clippy lints (#196)
• 2b2c352 refactor: limit dependency futures-util to tests and client-legacy (#192)
• 1bcd489 chore(test): make proxy test robust wrt IPv4/v6 (#195)
• d3b8440 fix(client): prefer IPv6 addresses before IPv4 even if resolver ordered diffe...
• See full diff in compare view

Sourced from tree-sitter's releases.

v0.25.5

What's Changed

• illumos has endian.h by @​tree-sitter-ci-bot in tree-sitter/tree-sitter#4451
• fix: wasi has endian.h by @​tree-sitter-ci-bot in tree-sitter/tree-sitter#4464
• Fix crash w/ goto_previous_sibling when parent node has leading extra child by @​tree-sitter-ci-bot in tree-sitter/tree-sitter#4473

Full Changelog: https://github.com/tree-sitter/tree-sitter/compare/v0.25.4...v0.25.5

• 460118b 0.25.5
• 42ca484 Fix hang in npm install script
• 75550c8 Fix crash w/ goto_previous_sibling when parent node has leading extra child (...
• 02f9c15 fix: wasi has endian.h
• d6701c6 illumos has endian.h
• See full diff in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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