Skip to content

chore: release bytesbuf v0.7.0 and 23 additional packages#599

Open
sgalkin wants to merge 5 commits into
mainfrom
release-fetch-hyper-0-5-0
Open

chore: release bytesbuf v0.7.0 and 23 additional packages#599
sgalkin wants to merge 5 commits into
mainfrom
release-fetch-hyper-0-5-0

Conversation

@sgalkin

@sgalkin sgalkin commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • release bytesbuf 0.7.0 and its dependent release cascade
  • apply SemVer-required version increments across 24 workspace crates
  • update workspace dependency requirements, lockfile entries, changelogs, and generated READMEs

Released versions

Crate Previous New
bytesbuf 0.6.0 0.7.0
bytesbuf_io 0.6.0 0.7.0
cachet 0.9.0 0.10.0
cachet_memory 0.5.0 0.5.1
cachet_service 0.2.8 0.2.9
cachet_tier 0.2.6 0.2.7
data_privacy 0.12.3 0.12.4
fetch 0.13.0 0.14.0
fetch_azure 0.3.0 0.4.0
fetch_hyper 0.4.6 0.5.0
fetch_tls 0.2.5 0.2.6
fundle 0.3.4 0.3.5
fundle_macros 0.3.4 0.3.5
fundle_macros_impl 0.3.4 0.3.5
http_extensions 0.7.0 0.8.0
layered 0.3.5 0.3.6
multitude 0.6.2 0.7.0
ohno 0.3.8 0.3.9
rest_over_grpc 0.1.0 0.1.1
seatbelt 0.6.0 0.6.1
seatbelt_http 0.5.0 0.6.0
templated_uri 0.3.4 0.3.5
templated_uri_macros 0.2.6 0.2.7
templated_uri_macros_impl 0.2.6 0.2.7

Copilot AI review requested due to automatic review settings July 23, 2026 14:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Release-cascade update for the Oxidizer Rust workspace, bumping bytesbuf to 0.7.0 and propagating semver-driven version increments and dependency requirement updates across 21 additional crates, along with regenerated release artifacts (READMEs, lockfile, changelogs).

Changes:

  • Bump versions for 22 workspace crates (including bytesbuf 0.6.0 -> 0.7.0, fetch 0.13.0 -> 0.14.0, templated_uri 0.3.4 -> 0.4.0).
  • Update per-crate changelogs with new release entries dated 2026-07-23.
  • Regenerate crate READMEs / docs.rs links and update workspace dependency versions and Cargo.lock.

Reviewed changes

Copilot reviewed 64 out of 65 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
crates/templated_uri/README.md Regenerated README link targets for templated_uri 0.4.0.
crates/templated_uri/CHANGELOG.md Add 0.4.0 release notes entry.
crates/templated_uri/Cargo.toml Bump crate version to 0.4.0.
crates/templated_uri_macros/CHANGELOG.md Add 0.2.7 release notes entry.
crates/templated_uri_macros/Cargo.toml Bump crate version to 0.2.7.
crates/templated_uri_macros_impl/CHANGELOG.md Add 0.2.7 release notes entry.
crates/templated_uri_macros_impl/Cargo.toml Bump crate version to 0.2.7.
crates/seatbelt/README.md Regenerated README link targets for seatbelt 0.6.1 and deps.
crates/seatbelt/CHANGELOG.md Add 0.6.1 release notes entry.
crates/seatbelt/Cargo.toml Bump crate version to 0.6.1.
crates/seatbelt_http/README.md Regenerated README link targets for seatbelt_http 0.5.1 and deps.
crates/seatbelt_http/CHANGELOG.md Add 0.5.1 release notes entry.
crates/seatbelt_http/Cargo.toml Bump crate version to 0.5.1.
crates/routerama/README.md Regenerated README dependency metadata blob.
crates/plurality/README.md Regenerated README dependency metadata blob.
crates/ohno/README.md Regenerated README link targets for ohno 0.3.9.
crates/ohno/CHANGELOG.md Add 0.3.9 release notes entry.
crates/ohno/Cargo.toml Bump crate version to 0.3.9.
crates/multitude/README.md Regenerated README link targets for multitude 0.6.3 and deps.
crates/multitude/CHANGELOG.md Add 0.6.3 release notes entry.
crates/multitude/Cargo.toml Bump crate version to 0.6.3.
crates/layered/README.md Regenerated README link targets for layered 0.3.6.
crates/layered/CHANGELOG.md Add 0.3.6 release notes entry.
crates/layered/Cargo.toml Bump crate version to 0.3.6.
crates/http_extensions/README.md Regenerated README link targets for http_extensions 0.7.1 and deps.
crates/http_extensions/CHANGELOG.md Add 0.7.1 release notes entry.
crates/http_extensions/Cargo.toml Bump crate version to 0.7.1.
crates/fundle/CHANGELOG.md Add 0.3.5 release notes entry.
crates/fundle/Cargo.toml Bump crate version to 0.3.5.
crates/fundle_macros/CHANGELOG.md Add 0.3.5 release notes entry.
crates/fundle_macros/Cargo.toml Bump crate version to 0.3.5.
crates/fundle_macros_impl/CHANGELOG.md Add 0.3.5 release notes entry.
crates/fundle_macros_impl/Cargo.toml Bump crate version to 0.3.5.
crates/fetch/README.md Regenerated README link targets for fetch 0.14.0 and deps.
crates/fetch/CHANGELOG.md Add 0.14.0 release notes entry.
crates/fetch/Cargo.toml Bump crate version to 0.14.0.
crates/fetch_tls/README.md Regenerated README link targets for fetch_tls 0.2.6.
crates/fetch_tls/CHANGELOG.md Add 0.2.6 release notes entry.
crates/fetch_tls/Cargo.toml Bump crate version to 0.2.6.
crates/fetch_hyper/README.md Regenerated README link targets for fetch_hyper 0.5.0 and deps.
crates/fetch_hyper/CHANGELOG.md Add 0.5.0 release notes entry.
crates/fetch_hyper/Cargo.toml Bump crate version to 0.5.0.
crates/fetch_azure/README.md Regenerated README link targets for fetch_azure 0.3.1 and deps.
crates/fetch_azure/CHANGELOG.md Add 0.3.1 release notes entry.
crates/fetch_azure/Cargo.toml Bump crate version to 0.3.1.
crates/cachet/README.md Regenerated README link targets for cachet 0.9.1 and deps.
crates/cachet/CHANGELOG.md Add 0.9.1 release notes entry.
crates/cachet/Cargo.toml Bump crate version to 0.9.1.
crates/cachet_tier/README.md Regenerated README link targets for cachet_tier 0.2.7.
crates/cachet_tier/CHANGELOG.md Add 0.2.7 release notes entry.
crates/cachet_tier/Cargo.toml Bump crate version to 0.2.7.
crates/cachet_service/README.md Regenerated README link targets for cachet_service 0.2.9 and deps.
crates/cachet_service/CHANGELOG.md Add 0.2.9 release notes entry.
crates/cachet_service/Cargo.toml Bump crate version to 0.2.9.
crates/cachet_memory/README.md Regenerated README link targets for cachet_memory 0.5.1 and deps.
crates/cachet_memory/CHANGELOG.md Add 0.5.1 release notes entry.
crates/cachet_memory/Cargo.toml Bump crate version to 0.5.1.
crates/bytesbuf/README.md Regenerated README link targets for bytesbuf 0.7.0.
crates/bytesbuf/CHANGELOG.md Add 0.7.0 release notes entry.
crates/bytesbuf/Cargo.toml Bump crate version to 0.7.0.
crates/bytesbuf_io/README.md Regenerated README link targets for bytesbuf_io 0.6.1.
crates/bytesbuf_io/CHANGELOG.md Add 0.6.1 release notes entry.
crates/bytesbuf_io/Cargo.toml Bump crate version to 0.6.1.
Cargo.toml Update workspace dependency versions for released crates.
Cargo.lock Update lockfile entries for released crate versions and dependency edges.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread crates/multitude/CHANGELOG.md Outdated
@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown

⚠️ Semver baseline could not be determined

cargo semver-checks could not determine the previous version-bump commit for 2 of 24 crate(s), so their version increment was not verified. No crate was found to be under-incremented; check the crate(s) below manually.

Crate Baseline Baseline commit This PR Minimum required Status
bytesbuf 0.6.0 ddbfcd1 0.7.0 0.6.1 ✅ ok
bytesbuf_io 0.6.0 ddbfcd1 0.7.0 0.6.1 ✅ ok
cachet 0.9.0 eefe110 0.10.0 0.9.1 ✅ ok
cachet_memory 0.5.0 eefe110 0.5.1 0.5.1 ✅ ok
cachet_service 0.2.8 542a32c 0.2.9 0.2.9 ✅ ok
cachet_tier 0.2.6 542a32c 0.2.7 0.2.7 ✅ ok
data_privacy 0.12.3 542a32c 0.12.4 0.12.4 ✅ ok
fetch 0.13.0 ddbfcd1 0.14.0 0.13.1 ✅ ok
fetch_azure 0.3.0 ddbfcd1 0.4.0 0.3.1 ✅ ok
fetch_hyper 0.4.6 ddbfcd1 0.5.0 0.4.7 ✅ ok
fetch_tls 0.2.5 542a32c 0.2.6 0.2.6 ✅ ok
fundle 0.3.4 542a32c 0.3.5 0.3.5 ✅ ok
fundle_macros ⚠️ 0.3.4 542a32c 0.3.5 ⚠️ baseline unknown — not verified
fundle_macros_impl 0.3.4 542a32c 0.3.5 0.3.5 ✅ ok
http_extensions 0.7.0 ddbfcd1 0.8.0 0.7.1 ✅ ok
layered 0.3.5 542a32c 0.3.6 0.3.6 ✅ ok
multitude 0.6.2 8ae7af6 0.7.0 0.6.3 ✅ ok
ohno 0.3.8 542a32c 0.3.9 0.3.9 ✅ ok
rest_over_grpc 0.1.0 5b39c89 0.1.1 0.1.1 ✅ ok
seatbelt 0.6.0 ddbfcd1 0.6.1 0.6.1 ✅ ok
seatbelt_http 0.5.0 ddbfcd1 0.6.0 0.5.1 ✅ ok
templated_uri 0.3.4 542a32c 0.3.5 0.3.5 ✅ ok
templated_uri_macros ⚠️ 0.2.6 542a32c 0.2.7 ⚠️ baseline unknown — not verified
templated_uri_macros_impl 0.2.6 542a32c 0.2.7 0.2.7 ✅ ok
⚠️ fundle_macros — baseline lookup detail
cargo semver-checks could not be evaluated against `542a32c00a8ce2cab3ed8876056aab847bc8c6c8` (v0.3.4). The version increment was NOT verified — check it manually.

cargo semver-checks did not produce a parseable result for 'fundle_macros' (exit 1). This usually means the tool is missing or the crate/baseline failed to build. Output:
error: no crates with library targets selected, nothing to semver-check
note: only library targets contain an API surface that can be checked for semver
note: skipped the following crates since they have no library target: fundle_macros

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: cargo_semver_checks::Check::check_release
   3: cargo_semver_checks::exit_on_error
   4: cargo_semver_checks::main
   5: std::sys::backtrace::__rust_begin_short_backtrace
   6: main

⚠️ templated_uri_macros — baseline lookup detail
cargo semver-checks could not be evaluated against `542a32c00a8ce2cab3ed8876056aab847bc8c6c8` (v0.2.6). The version increment was NOT verified — check it manually.

cargo semver-checks did not produce a parseable result for 'templated_uri_macros' (exit 1). This usually means the tool is missing or the crate/baseline failed to build. Output:
error: no crates with library targets selected, nothing to semver-check
note: only library targets contain an API surface that can be checked for semver
note: skipped the following crates since they have no library target: templated_uri_macros

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: cargo_semver_checks::Check::check_release
   3: cargo_semver_checks::exit_on_error
   4: cargo_semver_checks::main
   5: std::sys::backtrace::__rust_begin_short_backtrace
   6: main

The baseline could not be determined for the crate(s) above, so their version increments were not verified. This check is informational and does not block the merge.

View the check run

@codecov

codecov Bot commented Jul 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (5b39c89) to head (637cf7c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #599   +/-   ##
=======================================
  Coverage   100.0%   100.0%           
=======================================
  Files         440      440           
  Lines       42262    42262           
=======================================
  Hits        42262    42262           
Flag Coverage Δ
linux 91.2% <ø> (?)
linux-arm 91.0% <ø> (?)
windows 91.6% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread crates/templated_uri/Cargo.toml Outdated
Comment thread crates/multitude/CHANGELOG.md Outdated
Comment thread crates/fetch_hyper/CHANGELOG.md Outdated
@psandana

Copy link
Copy Markdown
Contributor

Cargo.lock shows recoverable (a workspace member) resolves ohno 0.3.8 -> 0.3.9, just like the ~9 other crates that received their own patch bump plus a "Now requires 0.3.9 of ohno" changelog entry in this PR (bytesbuf_io, cachet_tier, cachet_memory, fetch_tls, http_extensions, seatbelt, seatbelt_http, templated_uri, templated_uri_macros_impl). However, recoverable's own version and CHANGELOG were left untouched, and it doesn't appear in this PR's Released versions table.

Could you confirm the selection rule for this release cascade? If it's "every crate whose Cargo.lock entry for a bumped dependency changed gets a Maintenance republish", recoverable looks like it was missed; if there's a different rule (e.g. it has no other unreleased changes), it'd be good to make that criterion consistent/explicit so reviewers can verify future release PRs.

Copilot AI review requested due to automatic review settings July 24, 2026 05:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 64 out of 65 changed files in this pull request and generated no new comments.

Copilot AI review requested due to automatic review settings July 24, 2026 05:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 64 out of 65 changed files in this pull request and generated no new comments.

@sgalkin

sgalkin commented Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

Cargo.lock shows recoverable ... resolves ohno 0.3.8 -> 0.3.9 ... Could you confirm the selection rule for this release cascade?

Confirmed: recoverable should not be in this release set. Its ohno edge is under [dev-dependencies] only, while its published [dependencies] table is empty. Cargo.lock resolves workspace dev dependencies for tests, but that does not change recoverable's published dependency graph or require a maintenance republish. The release cascade follows published dependent edges, not every workspace lockfile entry that happens to resolve to a newer compatible version.

@ralfbiedert ralfbiedert left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Release versions, workspace dependencies, lockfile entries, changelogs, and 0.x SemVer cascades are consistent. The plurality 0.1.0 workspace dependency versus package 0.1.1 mismatch is pre-existing and out of scope.

Comment thread crates/bytesbuf_io/Cargo.toml Outdated
Sergey Galkin and others added 4 commits July 24, 2026 15:24
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 24, 2026 14:06
@sgalkin
sgalkin force-pushed the release-fetch-hyper-0-5-0 branch from 9d45587 to c27f63f Compare July 24, 2026 14:06
@sgalkin sgalkin changed the title chore: release bytesbuf v0.7.0 and 21 additional packages chore: release bytesbuf v0.7.0 and 23 additional packages Jul 24, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 68 out of 69 changed files in this pull request and generated 2 comments.

Comment thread crates/rest_over_grpc/CHANGELOG.md
Comment thread crates/rest_over_grpc/CHANGELOG.md Outdated
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 24, 2026 14:23

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 68 out of 69 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

crates/rest_over_grpc/CHANGELOG.md:12

  • The 0.1.1 changelog entry starts with “Initial release of rest_over_grpc…”, but this PR is a patch release (0.1.0 → 0.1.1). This makes the changelog misleading for consumers trying to see what actually changed in 0.1.1. Consider adding an (empty) Unreleased section, moving the “Initial release” notes under a 0.1.0 entry, and keeping the 0.1.1 entry focused on the actual deltas (e.g., dependency bumps like layered 0.3.6).

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.

6 participants