Skip to content

chore(release): prepare 58 coordinated crate releases - #739

Merged
Zac Walker (ZacWalk) merged 12 commits into
mainfrom
release/thread-aware-core-adoption
Sep 11, 2026
Merged

chore(release): prepare 58 coordinated crate releases#739
Zac Walker (ZacWalk) merged 12 commits into
mainfrom
release/thread-aware-core-adoption

Conversation

@ZacWalk

@ZacWalk Zac Walker (ZacWalk) commented Sep 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Summary

Prepare 58 coordinated crate releases, including the maintainer's macro-pinning and version-alignment commits. Initially rebased onto 8624f907 on main, including #744 and the merged #733 runtime-recording work. Subsequently merged main at 704eba82 in b1b8dc17, including #722 (compressors) and #745 (metabench support identifiers), without rewriting the PR history. All 79 pre-merge package versions are preserved; the new compressors package retains upstream 0.1.0. No new release versions were chosen during the merge.

  • Release thread_aware 0.12.0 and affected consumers for thread_aware_core adoption; retain thread_aware_core 0.1.1 as a compatible addition.
  • Release rest_over_grpc 0.2.1, including the query-field nesting-depth fix from fix(rest_over_grpc): bound query field path nesting depth #729.
  • Preserve the observed family at 0.26.0, fundle at 0.4.0, and data-privacy facade/macros at 0.13.0.
  • Preserve the later maintainer updates: exact macro pins; the ohno family at 0.5.2; internity and macros at 0.2.1; metabench and macros at 0.1.1; multitude and macros at 0.10.0; and templated-uri and macros at 0.6.0.
  • Retain data_privacy_core 0.1.2, plurality 0.2.2, and recoverable 0.2.0 without release bumps.
  • Preserve the reviewed release-note cleanup: remove CI-only and misattributed feature notes, restore preambles, normalize new categories, preserve historical entries, and describe fix(rest_over_grpc): bound query field path nesting depth #729/fix(observed_macros): reject mutable-reference event fields #730 once each. Retain the verified http_path_template 0.2.0 publication date, 2026-07-22.
  • Address remaining feedback in 18de2ac3: correct the uniflight stampede keyword and qualify optional dependency notes by their features in rest_over_grpc and seatbelt_http.
  • Reconcile registry lockfile resolution in f3d71c7e: restore seven windows-sys references and the related tempfile/getrandom reference to main, without changing any package versions.

Relative to current main, this is release metadata and generated documentation, plus the bytesbuf rustdoc URL correction. The incoming implementation changes from #733, #722, and #745 come from main and were preserved. The root manifest conflict was resolved by retaining the release's fetch package versions and main's new flate2 dependency.

Required Release Review

The author confirmed on 2026-09-10 that performables and seismograph_cli must remain at upstream 0.1.0; do not add release bumps for them. This is an intentional exception to the release planner's normal dependent cascade. Their initial-publication handling and dependency closure are specified below; keeping these versions does not mean that their publication can be skipped.

The initial review compared 46 ordinary libraries against previous version-bump commits with cargo semver-checks --all-features --release-type patch. Manual evidence also covered the public ThreadAware identity migration, public Syn 2-to-3 helper types, the observed mutable-reference macro input restriction, and ohno's warning-policy caveat.

The pre-merge SemVer report identifies 10 proc-macro packages and 26 ordinary consumers requiring manual compatibility review, with no reported under-increment. Comparing the pre-rebase head 826feb24 with 65cc1af8 shows no changes in the macro packages or routerama_build, so the earlier macro-source evidence survives that rebase. The subsequent merge brings in #745's metabench macro support-identifier fix unchanged from main; its unit, expansion, and compile-contract tests passed against the release versions. Prior evidence does not establish compatibility of the consumer changes introduced by #733 or replace the fresh merged-head report.

Final release review must confirm the macro/consumer classifications, particularly the patch boundaries of internity 0.2.1 and arty_executor 0.1.2, routerama parser/macro compatibility, ohno's generated-code warning policy, and the post-#733 public-type/runtime implications. The automated SemVer warning is informational; passing builds and resolved review threads do not replace this release signoff.

Post-rebase Validation

  • Passed at 65cc1af8: locked workspace cargo check --all-features.
  • Passed at 65cc1af8: just clippy for the workspace, all features and targets.
  • Passed at 65cc1af8: 811 selected tests across rallocator, thread-aware, REST-over-gRPC, internity, and metabench packages (43 binaries).
  • Passed at 65cc1af8: pinned formatting checks across all 79 workspace packages, README generation, whitespace checks, and editor diagnostics.
  • Passed: comparison of surviving package versions against the exact pre-rebase head 826feb24; all 72 match. Current exact/caret workspace dependency requirements match target versions.
  • Confirmed: the old thread_heap_usage_includes_remote_allocations test is absent after feat(seismograph): introduce runtime recording #733. No test was disabled or assertion weakened in this release branch.
  • The 65cc1af8 CI run completed with 58 successful checks and one skipped check.
  • Passed for the feedback fix 18de2ac3: locked Cargo metadata verification, just anvil-cargo-sort, just anvil-clippy, just anvil-fmt --fix, just anvil-readme --fix, just anvil-spellcheck, whitespace checks, and editor diagnostics. Regeneration produced no additional source/README changes. The local spelling-tool prerequisite is now installed.
  • Passed for the lockfile fix f3d71c7e: full locked/offline Cargo metadata, just anvil-clippy (all targets/features), just anvil-fmt --fix, just anvil-readme --fix, just anvil-spellcheck, whitespace checks, and editor diagnostics. All 568 registry-package lock entries exactly match main; all 79 non-registry entries remain unchanged from 18de2ac3. ring retains its required windows-sys 0.52.0 dependency.
  • Fresh CI for the latest head must finish successfully; results from preceding commits are not a substitute.

Before the rebase, selected runs passed 2,691 tests for release consumers and 969 tests including thread-aware and ohno. Those results are historical.

Main-merge Validation

For b1b8dc17, merging main at 704eba82:

  • Passed: full locked/offline Cargo metadata for 80 workspace packages. All 79 prior manifest versions are unchanged; compressors remains 0.1.0.
  • Passed: all 576 registry-package lock entries exactly match incoming main. The Windows dependency-resolution correction is preserved.
  • Passed: 553 unit/integration tests across compressors, metabench, metabench_macros, and metabench_macros_impl; none skipped.
  • Passed: 26 doctests across those packages, with seven existing ignored examples.
  • Passed: generated Anvil workspace Clippy (all targets/features), manifest sorting, formatting, README regeneration, spelling, whitespace checks, and editor diagnostics.
  • Regenerated the compressors README to link to the release's bytesbuf 0.10.0; incoming compressors and metabench macro implementation code matches main.
  • Confirmed: the release selector still selects 58 bumped packages against current main. No release versions were added or changed.
  • GitHub reports the conflict resolved. Fresh CI and approval of the latest reviewable push are required; prior checks do not validate this merge.

Publication

This PR prepares releases only. No crates have been published or yanked as part of this work.

Registry checks on 2026-09-10 found all seven new #733 packages unpublished:

  • performables
  • seismograph
  • seismograph_protocol
  • seismograph_io
  • seismograph_cli
  • seismograph_runtime
  • seismograph_rallocator

Preserve their initial versions. The normal comparison against current main selects the 58 version-bumped packages and excludes these seven initial packages and the newly merged compressors 0.1.0. The existing 58 releases require seismograph_protocol, seismograph, performables, and seismograph_io; shipping the CLI additionally requires the runtime/rallocator helpers. Publish prerequisites before their consumers in Cargo dependency order. The compressors registry/publication status was not checked in this merge update.

Before merging, the publishing maintainer must confirm one of these paths:

  1. Complete and verify the feat(seismograph): introduce runtime recording #733 initial publications, then publish the normal 58-package release set; or
  2. Explicitly include the required initial packages in a catch-up publication together with the 58 bumped packages. After merging feat(compressors): add streaming compression crate #722, the repository's Get-PackagesWithVersionChanges helper selects exactly 66 packages when compared against pre-feat(seismograph): introduce runtime recording #733 commit 70bd5aafadb9b11fc45d8977bd808066e574b8de: the 58 bumped packages, the seven feat(seismograph): introduce runtime recording #733 packages, and compressors. Confirm actual registry availability, equivalent selection, and dependency ordering in the publishing pipeline before execution; the earlier 65-package count applied before compressors joined main.

.ado/pipelines/publish.yml exposes previousVersion (default HEAD^) but delegates publishing to the external ox-sdk template. Its catch-up behavior has not been verified or executed here. The official pipeline triggers on main and defaults executePublish to true, so publication selection must be confirmed before merge, not deferred until after it.

Do not merge until required checks, final release review, and the initial-publication plan are confirmed. Do not rerun the release driver on the already-bumped branch merely to include these initial packages; that would re-increment existing releases rather than preserve the approved version plan.

Tooling Follow-up

The release generator inserts sections ahead of preambles, combines curated headings with list-style categories, and uses tag-based history that can lag declared releases. The release artifacts have been repaired; generator behavior and regression tests remain separate follow-up work.

Copilot AI lite review requested due to automatic review settings September 7, 2026 17:17
Copilot AI reviewed Sep 7, 2026
View reviewed changes

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.

🟡 Changes recommended

A few release notes entries are internally inconsistent/misleading (notably thread_aware_core 0.1.1 marked breaking despite a patch bump, and unrelated PR #686 “split” notes in other crates’ changelogs), which should be corrected before publishing.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR prepares a coordinated multi-crate release train by updating crate versions, dependency version requirements, changelog entries, and regenerated crate READMEs (doc links/hashes), plus the workspace dependency version pins in the root Cargo.toml.

Changes:

  • Bump crate versions and align workspace dependency version requirements for the release set.
  • Add new release entries to per-crate CHANGELOG.md files.
  • Regenerate crate README.md files (doc2readme link/version updates).
File summaries
File Description
Cargo.toml Update workspace dependency version pins for the coordinated releases.
crates/anyspawn/Cargo.toml Bump crate version for release.
crates/anyspawn/CHANGELOG.md Add release notes entry.
crates/anyspawn/README.md Regenerate README doc links for new version.
crates/anyspawn_azure/Cargo.toml Bump crate version for release.
crates/anyspawn_azure/CHANGELOG.md Add release notes entry.
crates/anyspawn_azure/README.md Regenerate README doc links for new version.
crates/arty/Cargo.toml Bump crate version for release.
crates/arty/CHANGELOG.md Add release notes entry.
crates/arty/README.md Regenerate README metadata block.
crates/arty_executor/Cargo.toml Bump crate version for release.
crates/arty_executor/CHANGELOG.md Add release notes entry.
crates/bytesbuf/Cargo.toml Bump crate version for release.
crates/bytesbuf/CHANGELOG.md Add release notes entry.
crates/bytesbuf/README.md Regenerate README doc links for new version.
crates/bytesbuf_io/Cargo.toml Bump crate version for release.
crates/bytesbuf_io/CHANGELOG.md Add release notes entry.
crates/bytesbuf_io/README.md Regenerate README doc links for new version.
crates/cachet/Cargo.toml Bump crate version for release.
crates/cachet/CHANGELOG.md Add release notes entry.
crates/cachet/README.md Regenerate README doc links for new version.
crates/cachet_memory/Cargo.toml Bump crate version for release.
crates/cachet_memory/CHANGELOG.md Add release notes entry.
crates/cachet_memory/README.md Regenerate README doc links for new version.
crates/cachet_service/Cargo.toml Bump crate version for release.
crates/cachet_service/CHANGELOG.md Add release notes entry.
crates/cachet_service/README.md Regenerate README doc links for new version.
crates/cachet_tier/Cargo.toml Bump crate version for release.
crates/cachet_tier/CHANGELOG.md Add release notes entry.
crates/cachet_tier/README.md Regenerate README doc links for new version.
crates/data_privacy/Cargo.toml Bump crate version for release.
crates/data_privacy/CHANGELOG.md Add release notes entry.
crates/data_privacy/README.md Regenerate README doc links for new version.
crates/data_privacy_core/Cargo.toml Bump crate version for release.
crates/data_privacy_core/CHANGELOG.md Add release notes entry.
crates/data_privacy_core/README.md Regenerate README doc links for new version.
crates/data_privacy_macros/Cargo.toml Bump crate version for release.
crates/data_privacy_macros/CHANGELOG.md Add release notes entry.
crates/data_privacy_macros_impl/Cargo.toml Bump crate version for release.
crates/data_privacy_macros_impl/CHANGELOG.md Add release notes entry.
crates/fetch/Cargo.toml Bump crate version for release.
crates/fetch/CHANGELOG.md Add release notes entry.
crates/fetch/README.md Regenerate README doc links for new version.
crates/fetch_azure/Cargo.toml Bump crate version for release.
crates/fetch_azure/CHANGELOG.md Add release notes entry.
crates/fetch_azure/README.md Regenerate README doc links for new version.
crates/fetch_hyper/Cargo.toml Bump crate version for release.
crates/fetch_hyper/CHANGELOG.md Add release notes entry.
crates/fetch_hyper/README.md Regenerate README doc links for new version.
crates/fetch_tls/Cargo.toml Bump crate version for release.
crates/fetch_tls/CHANGELOG.md Add release notes entry.
crates/fetch_tls/README.md Regenerate README doc links for new version.
crates/fetch_winhttp/Cargo.toml Bump crate version for release.
crates/fetch_winhttp/CHANGELOG.md Add release notes entry.
crates/fetch_winhttp_impl/Cargo.toml Bump crate version for release.
crates/fetch_winhttp_impl/CHANGELOG.md Add release notes entry.
crates/fundle/Cargo.toml Bump crate version for release.
crates/fundle/CHANGELOG.md Add release notes entry.
crates/fundle_macros/Cargo.toml Bump crate version for release.
crates/fundle_macros/CHANGELOG.md Add release notes entry.
crates/fundle_macros_impl/Cargo.toml Bump crate version for release.
crates/fundle_macros_impl/CHANGELOG.md Add release notes entry.
crates/http_extensions/Cargo.toml Bump crate version for release.
crates/http_extensions/CHANGELOG.md Add release notes entry.
crates/http_extensions/README.md Regenerate README doc links for new version.
crates/http_path_template/Cargo.toml Bump crate version for release.
crates/http_path_template/CHANGELOG.md Add release notes entry.
crates/http_path_template/README.md Regenerate README doc links for new version.
crates/layered/Cargo.toml Bump crate version for release.
crates/layered/CHANGELOG.md Add release notes entry.
crates/layered/README.md Regenerate README doc links for new version.
crates/multitude/Cargo.toml Bump crate version for release.
crates/multitude/CHANGELOG.md Add release notes entry.
crates/multitude_macros/Cargo.toml Bump crate version for release.
crates/multitude_macros/CHANGELOG.md Add new changelog file/entry for release.
crates/multitude_macros_impl/Cargo.toml Bump crate version for release.
crates/multitude_macros_impl/CHANGELOG.md Add new changelog file/entry for release.
crates/msvc_spectre_libs/Cargo.toml Bump crate version for release.
crates/msvc_spectre_libs/CHANGELOG.md Add new changelog file/entry for release.
crates/msvc_spectre_libs_build/Cargo.toml Bump crate version for release.
crates/msvc_spectre_libs_build/CHANGELOG.md Add new changelog file/entry for release.
crates/msvc_spectre_libs_build/README.md Regenerate README doc links for new version.
crates/observed/Cargo.toml Bump crate version for release.
crates/observed/CHANGELOG.md Add release notes entry (and reorganize header placement).
crates/observed/README.md Regenerate README doc links for new version.
crates/observed_macros/Cargo.toml Bump crate version for release.
crates/observed_macros/CHANGELOG.md Add release notes entry (macro compatibility note).
crates/observed_macros_impl/Cargo.toml Bump crate version for release.
crates/observed_macros_impl/CHANGELOG.md Add release notes entry (macro behavior change note).
crates/observed_utils/Cargo.toml Bump crate version for release.
crates/observed_utils/CHANGELOG.md Add release notes entry.
crates/observed_utils/README.md Regenerate README doc links for new version.
crates/ohno/Cargo.toml Bump crate version for release.
crates/ohno/CHANGELOG.md Add release notes entry.
crates/ohno/README.md Regenerate README doc links for new version.
crates/ohno_macros/Cargo.toml Bump crate version for release.
crates/ohno_macros/CHANGELOG.md Add release notes entry.
crates/ohno_macros_impl/Cargo.toml Bump crate version for release.
crates/ohno_macros_impl/CHANGELOG.md Add release notes entry.
crates/plurality/Cargo.toml Bump crate version for release.
crates/plurality/CHANGELOG.md Add release notes entry.
crates/plurality/README.md Regenerate README doc links for new version.
crates/recoverable/Cargo.toml Bump crate version for release.
crates/recoverable/CHANGELOG.md Add release notes entry.
crates/recoverable/README.md Regenerate README doc links for new version.
crates/rest_over_grpc/Cargo.toml Bump crate version for release.
crates/rest_over_grpc/CHANGELOG.md Add release notes entry (includes depth-limit fix note).
crates/rest_over_grpc/README.md Regenerate README doc links for new version.
crates/routerama/Cargo.toml Bump crate version for release.
crates/routerama/CHANGELOG.md Add release notes entry.
crates/routerama/README.md Regenerate README doc links for new version.
crates/routerama_build/Cargo.toml Bump crate version for release.
crates/routerama_build/CHANGELOG.md Add release notes entry.
crates/routerama_build/README.md Regenerate README doc links for new version.
crates/routerama_macros/Cargo.toml Bump crate version for release.
crates/routerama_macros/CHANGELOG.md Add release notes entry.
crates/seatbelt/Cargo.toml Bump crate version for release.
crates/seatbelt/CHANGELOG.md Add release notes entry.
crates/seatbelt/README.md Regenerate README doc links for new version.
crates/seatbelt_http/Cargo.toml Bump crate version for release.
crates/seatbelt_http/CHANGELOG.md Add release notes entry.
crates/seatbelt_http/README.md Regenerate README doc links for new version.
crates/templated_uri/Cargo.toml Bump crate version for release.
crates/templated_uri/CHANGELOG.md Add release notes entry.
crates/templated_uri/README.md Regenerate README doc links for new version.
crates/templated_uri_macros/Cargo.toml Bump crate version for release.
crates/templated_uri_macros/CHANGELOG.md Add release notes entry.
crates/templated_uri_macros_impl/Cargo.toml Bump crate version for release.
crates/templated_uri_macros_impl/CHANGELOG.md Add release notes entry.
crates/thread_aware/Cargo.toml Bump crate version for release.
crates/thread_aware/CHANGELOG.md Add release notes entry.
crates/thread_aware/README.md Regenerate README doc links for new version.
crates/thread_aware_core/Cargo.toml Bump crate version for release.
crates/thread_aware_core/CHANGELOG.md Add release notes entry.
crates/thread_aware_core/README.md Regenerate README doc links for new version.
crates/thread_aware_macros/Cargo.toml Bump crate version for release.
crates/thread_aware_macros/CHANGELOG.md Add release notes entry.
crates/thread_aware_macros_impl/Cargo.toml Bump crate version for release.
crates/thread_aware_macros_impl/CHANGELOG.md Add release notes entry.
crates/tick/Cargo.toml Bump crate version for release.
crates/tick/CHANGELOG.md Add release notes entry.
crates/tick/README.md Regenerate README doc links for new version.
crates/uniflight/Cargo.toml Bump crate version for release.
crates/uniflight/CHANGELOG.md Add release notes entry.
crates/uniflight/README.md Regenerate README doc links for new version.
Review details
  • Files reviewed: 146/147 changed files
  • Comments generated: 3
  • Review effort level: Lite

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread crates/data_privacy_macros_impl/CHANGELOG.md Outdated
Comment thread crates/fundle_macros_impl/CHANGELOG.md Outdated
Comment thread crates/thread_aware_core/CHANGELOG.md Outdated
@github-actions

github-actions Bot commented Sep 7, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ Manual proc-macro SemVer review required

cargo semver-checks intentionally does not analyse proc-macro-only targets. 36 of 58 publishing crate(s) require manual review either for their own procedural macro contract or because they directly consume a manually reviewed breaking release. Ordinary libraries retain their automated result, and review advances to the next dependency edge only when the current release is breaking.

Crate Baseline Baseline commit This PR Minimum required Status
anyspawn 0.8.0 d170a41 0.9.0 0.8.1 ⚠️ automated check ok; manual proc-macro chain review required
anyspawn_azure 0.3.0 d170a41 0.4.0 0.3.1 ⚠️ automated check ok; manual proc-macro chain review required
arty 0.2.0 efd8178 0.3.0 0.2.1 ⚠️ automated check ok; manual proc-macro chain review required
arty_executor 0.1.1 d170a41 0.1.2 0.1.2 ⚠️ automated check ok; manual proc-macro chain review required
bytesbuf 0.9.0 d170a41 0.10.0 0.9.1 ⚠️ automated check ok; manual proc-macro chain review required
bytesbuf_io 0.9.0 d170a41 0.10.0 0.9.1 ⚠️ automated check ok; manual proc-macro chain review required
cachet 0.13.0 d170a41 0.14.0 0.13.1 ⚠️ automated check ok; manual proc-macro chain review required
cachet_memory 0.7.0 d170a41 0.8.0 0.7.1 ⚠️ automated check ok; manual proc-macro chain review required
cachet_service 0.5.0 d170a41 0.5.1 0.5.1 ✅ ok
cachet_tier 0.5.0 d170a41 0.5.1 0.5.1 ✅ ok
data_privacy 0.12.4 94229b8 0.13.0 0.12.5 ⚠️ automated check ok; manual proc-macro chain review required
data_privacy_macros 0.10.3 542a32c 0.13.0 — ⚠️ manual proc-macro review required
data_privacy_macros_impl 0.10.3 542a32c 0.13.0 0.10.4 ✅ ok
fetch 0.16.1 356dc63 0.17.0 0.16.2 ⚠️ automated check ok; manual proc-macro chain review required
fetch_azure 0.6.1 356dc63 0.7.0 0.6.2 ⚠️ automated check ok; manual proc-macro chain review required
fetch_hyper 0.7.1 356dc63 0.8.0 0.7.2 ⚠️ automated check ok; manual proc-macro chain review required
fetch_tls 0.4.0 d170a41 0.4.1 0.4.1 ✅ ok
fetch_winhttp 0.1.1 5899abe 0.2.0 0.1.2 ⚠️ automated check ok; manual proc-macro chain review required
fetch_winhttp_impl 0.1.1 5899abe 0.2.0 0.1.2 ⚠️ automated check ok; manual proc-macro chain review required
fundle 0.3.5 94229b8 0.4.0 0.3.6 ⚠️ automated check ok; manual proc-macro chain review required
fundle_macros 0.3.5 94229b8 0.4.0 — ⚠️ manual proc-macro review required
fundle_macros_impl 0.3.5 94229b8 0.4.0 0.3.6 ✅ ok
http_extensions 0.10.0 d170a41 0.11.0 0.10.1 ⚠️ automated check ok; manual proc-macro chain review required
http_path_template 0.2.0 1feffd7 0.2.1 0.2.1 ✅ ok
internity 0.2.0 8538b4f 0.2.1 0.2.1 ⚠️ automated check ok; manual proc-macro chain review required
internity_macros 0.1.0 0de29c6 0.2.1 — ⚠️ manual proc-macro review required
internity_macros_impl 0.1.0 0de29c6 0.2.1 0.1.1 ✅ ok
layered 0.3.6 94229b8 0.3.7 0.3.7 ✅ ok
metabench 0.1.0 86b3b65 0.1.1 0.1.1 ✅ ok
metabench_macros 0.1.0 86b3b65 0.1.1 — ⚠️ manual proc-macro review required
metabench_macros_impl 0.1.0 86b3b65 0.1.1 0.1.1 ✅ ok
msvc_spectre_libs 0.2.0 400e97e 0.2.1 0.2.1 ✅ ok
msvc_spectre_libs_build 0.1.0 400e97e 0.1.1 0.1.1 ✅ ok
multitude 0.9.0 d170a41 0.10.0 0.9.1 ⚠️ automated check ok; manual proc-macro chain review required
multitude_macros 0.1.1 7c185b4 0.10.0 — ⚠️ manual proc-macro review required
multitude_macros_impl 0.1.1 7c185b4 0.10.0 0.1.2 ✅ ok
observed 0.25.0 d170a41 0.26.0 0.25.1 ⚠️ automated check ok; manual proc-macro chain review required
observed_macros 0.24.0 7918922 0.26.0 — ⚠️ manual proc-macro review required
observed_macros_impl 0.24.0 6ac5bdc 0.26.0 0.24.1 ✅ ok
observed_utils 0.2.0 d170a41 0.3.0 0.2.1 ⚠️ automated check ok; manual proc-macro chain review required
ohno 0.5.0 d170a41 0.5.2 0.5.1 ✅ ok
ohno_macros 0.5.0 d170a41 0.5.2 — ⚠️ manual proc-macro review required
ohno_macros_impl 0.5.1 d170a41 0.5.2 0.5.2 ✅ ok
rest_over_grpc 0.2.0 b650922 0.2.1 0.2.1 ✅ ok
routerama 0.1.0 1feffd7 0.1.1 0.1.1 ✅ ok
routerama_build 0.1.0 1feffd7 0.1.1 0.1.1 ✅ ok
routerama_macros 0.1.0 1feffd7 0.1.1 — ⚠️ manual proc-macro review required
seatbelt 0.8.0 d170a41 0.9.0 0.8.1 ⚠️ automated check ok; manual proc-macro chain review required
seatbelt_http 0.8.0 d170a41 0.9.0 0.8.1 ⚠️ automated check ok; manual proc-macro chain review required
templated_uri 0.5.0 d170a41 0.6.0 0.5.1 ⚠️ automated check ok; manual proc-macro chain review required
templated_uri_macros 0.5.0 d170a41 0.6.0 — ⚠️ manual proc-macro review required
templated_uri_macros_impl 0.5.0 d170a41 0.6.0 0.5.1 ✅ ok
thread_aware 0.11.0 d170a41 0.12.0 0.11.1 ⚠️ automated check ok; manual proc-macro chain review required
thread_aware_core 0.1.0 7fc5cd5 0.1.1 0.1.1 ✅ ok
thread_aware_macros 0.11.0 d170a41 0.12.0 — ⚠️ manual proc-macro review required
thread_aware_macros_impl 0.11.0 d170a41 0.12.0 0.11.1 ✅ ok
tick 0.6.0 d170a41 0.7.0 0.6.1 ⚠️ automated check ok; manual proc-macro chain review required
uniflight 0.5.0 d170a41 0.6.0 0.5.1 ⚠️ automated check ok; manual proc-macro chain review required
⚠️ anyspawn — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ anyspawn_azure — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `anyspawn, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ arty — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ arty_executor — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ bytesbuf — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ bytesbuf_io — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `bytesbuf` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ cachet — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `anyspawn, bytesbuf, cachet_memory, tick, uniflight` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ cachet_memory — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ data_privacy — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `data_privacy_macros` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ data_privacy_macros — manual proc-macro review detail 
`data_privacy_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ fetch — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `anyspawn, bytesbuf, data_privacy, fetch_hyper, fundle, http_extensions, seatbelt, seatbelt_http, templated_uri, thread_aware, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ fetch_azure — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `bytesbuf, fetch` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ fetch_hyper — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `anyspawn, bytesbuf, http_extensions, seatbelt, templated_uri, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ fetch_winhttp — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `fetch_winhttp_impl` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ fetch_winhttp_impl — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `bytesbuf, bytesbuf_io, fetch, http_extensions, observed, thread_aware, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ fundle — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `fundle_macros` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ fundle_macros — manual proc-macro review detail 
`fundle_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ http_extensions — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `bytesbuf, templated_uri, thread_aware, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ internity — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `internity_macros` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ internity_macros — manual proc-macro review detail 
`internity_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ metabench_macros — manual proc-macro review detail 
`metabench_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ multitude — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `bytesbuf, multitude_macros` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ multitude_macros — manual proc-macro review detail 
`multitude_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ observed — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `data_privacy, observed_macros, thread_aware, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ observed_macros — manual proc-macro review detail 
`observed_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ observed_utils — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `data_privacy, observed` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ ohno_macros — manual proc-macro review detail 
`ohno_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ routerama_macros — manual proc-macro review detail 
`routerama_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ seatbelt — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ seatbelt_http — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `http_extensions, seatbelt, templated_uri, tick` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ templated_uri — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `data_privacy, templated_uri_macros` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ templated_uri_macros — manual proc-macro review detail 
`templated_uri_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ thread_aware — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware_macros` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ thread_aware_macros — manual proc-macro review detail 
`thread_aware_macros` is a proc-macro-only crate. cargo-semver-checks intentionally skips proc-macro targets because they have no supported library API surface. Review exported macro names, accepted input syntax, diagnostics, and generated output manually; build and test results do not establish public API SemVer compatibility.
⚠️ tick — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ uniflight — manual proc-macro propagation review detail 
Manual review is also required because direct dependency release(s) `thread_aware` were manually reviewed as breaking in the proc-macro compatibility chain. cargo-semver-checks still ran for this ordinary library when possible, but cannot prove whether the procedural macro contract is re-exported or otherwise exposed. If this crate's release is breaking, review continues to its direct published consumers; otherwise propagation stops here.
⚠️ compressors — missing direct-consumer review 
`thread_aware` has a breaking release in the manual proc-macro compatibility chain, but direct published consumer `compressors` is not in this PR's publishing set. Run the release planner so the consumer receives its patch cascade floor, cargo-semver-checks analysis, and mandatory manual review.
⚠️ compressors — missing direct-consumer review 
`bytesbuf` has a breaking release in the manual proc-macro compatibility chain, but direct published consumer `compressors` is not in this PR's publishing set. Run the release planner so the consumer receives its patch cascade floor, cargo-semver-checks analysis, and mandatory manual review.

Proc-macro API compatibility must be reviewed manually; successful builds and tests do not establish SemVer compatibility. This check is informational and does not block the merge.

At least one direct published consumer that requires review is absent from the publishing set. Re-run the release planner before merging.

View the check run

@codecov

codecov Bot commented Sep 7, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (704eba8) to head (b1b8dc1).

Additional details and impacted files 
@@          Coverage Diff           @@
##            main     #739   +/-   ##
======================================
  Coverage   99.9%   100.0%           
======================================
  Files        634      634           
  Lines      84746    84746           
======================================
+ Hits       84744    84746    +2     
+ Misses         2        0    -2
Flag Coverage Δ
linux 100.0% <ø> (?)
linux-arm 100.0% <ø> (?)
windows 100.0% <ø> (?)

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.

Zac Walker (ZacWalk) added a commit that referenced this pull request Sep 7, 2026
@ZacWalk
docs(release): correct crate-specific release notes
b6cb206 
Address PR #739 review feedback: describe shared macro test-helper adoption accurately, document public Syn type upgrades, and classify thread_aware_core 0.1.1 as compatible.
Copilot AI review requested due to automatic review settings September 7, 2026 18:38
Copilot AI reviewed Sep 7, 2026
View reviewed changes

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.

🔵 Needs a closer look

Some release notes appear misleading (e.g., patch releases described as “initial release” / section structure issues), which should be corrected before publishing.

Review details

Suppressed comments (4)

Previously missed (4) — in code that hasn't changed since the last review.

crates/http_path_template/CHANGELOG.md:10

  • This 0.2.1 entry describes the “Initial release” of http_path_template and introduces its core API surface, but this PR is bumping the crate from 0.2.0 → 0.2.1. That wording makes the 0.2.1 release notes misleading; consider restoring/moving the initial-release bullets under a 0.2.0 section and leaving 0.2.1 to cover only the delta since 0.2.0.
    crates/observed_macros/CHANGELOG.md:15
  • The “### Added” section claims this is the “Initial release” of observed_macros, but this PR is bumping the crate from 0.24.0 → 0.25.0. Rewording this bullet to describe the crate’s role (and the impl split) avoids implying first publication in 0.25.0.
    crates/observed_macros_impl/CHANGELOG.md:10
  • This entry says “Initial release of observed_macros_impl”, but the crate version is being bumped from 0.24.0 → 0.25.0 in this PR. Rewording avoids implying first publication in 0.25.0 while still explaining the shim/impl split.
    crates/thread_aware_core/CHANGELOG.md:18
  • The “🔄 Continuous Integration” entry is currently still inside the “### Fixed” section (because it’s a list item, not a heading), which misclassifies this change under “Fixed”. Make CI its own heading to keep the changelog’s section structure accurate.
  • Files reviewed: 146/147 changed files
  • Comments generated: 0 new
  • Review effort level: Lite

Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/observed_macros_impl/CHANGELOG.md Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/observed_macros/Cargo.toml Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/fundle_macros/Cargo.toml Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/fundle/Cargo.toml Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/data_privacy_macros/Cargo.toml Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/data_privacy_core/CHANGELOG.md Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/data_privacy/Cargo.toml Outdated
Vaiz
Evgenii (Vaiz) reviewed Sep 8, 2026
View reviewed changes
Comment thread Cargo.toml Outdated
Zac Walker (ZacWalk) added a commit that referenced this pull request Sep 8, 2026
@ZacWalk
chore(release): align crate families and refine release notes
160aa2a 
Address maintainer feedback on PR #739: align observed to 0.26, fundle to 0.4, and data-privacy to 0.13. Keep data_privacy_core at 0.1.2 and propagate exposed data-privacy types to templated_uri 0.6.0.

Remove CI-only release entries and correct initial-release notes. Validate the 54-package graph, workspace Clippy, formatting, README generation, and 936 selected tests.
Copilot AI review requested due to automatic review settings September 8, 2026 11:03
@ZacWalk Zac Walker (ZacWalk) changed the title chore(release): prepare 55 coordinated crate releases chore(release): prepare 54 coordinated crate releases Sep 8, 2026
@ZacWalk

Zac Walker (ZacWalk) commented Sep 8, 2026

Copy link
Copy Markdown
Member Author

🤖 Updated in 160aa2a: all eight maintainer comments are addressed. The additional bot findings are also corrected: http_path_template initial API notes are under 0.2.0, observed macro notes describe their role/split without claiming first publication, and the misplaced thread_aware_core CI entry was removed. Local validation passed: 936 selected tests, workspace Clippy/check, formatting, README generation, and the 54-package version/dependency audit. Coverage follow-up: Windows Anvil coverage passed at 1492764 (job 101821357543), then rallocator fell to 99.9% after b6cb206 changed only three changelogs. The new push reruns CI; no allocator code or coverage threshold was changed. Exact missed lines remain undiagnosed, so a repeated failure still needs investigation before merge.

Copilot AI reviewed Sep 8, 2026
View reviewed changes

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.

🟡 Changes recommended

Several changelog entries introduce formatting/information issues (empty entries and inconsistent section structure) that should be corrected before publishing.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (1)

crates/multitude_macros_impl/CHANGELOG.md:4

  • This changelog entry is currently just a version header with no notes. If this release is intentionally a no-op/version-alignment bump, it’s still helpful to record that (e.g., a short “technical release” maintenance note) so consumers aren’t left guessing what changed.
  • Files reviewed: 143/144 changed files
  • Comments generated: 3
  • Review effort level: Lite

Comment thread crates/http_path_template/CHANGELOG.md
Comment thread crates/recoverable/CHANGELOG.md Outdated
Comment thread crates/templated_uri/CHANGELOG.md Outdated
wukchung
martinhavelka (wukchung) reviewed Sep 8, 2026
View reviewed changes
Comment thread crates/observed_macros_impl/CHANGELOG.md Outdated
Comment thread crates/data_privacy_macros/CHANGELOG.md Outdated
Comment thread crates/plurality/CHANGELOG.md Outdated
psandana
Pato Sandaña (psandana) reviewed Sep 9, 2026
View reviewed changes
Comment thread crates/data_privacy_macros_impl/CHANGELOG.md Outdated
psandana
Pato Sandaña (psandana) reviewed Sep 9, 2026
View reviewed changes
Comment thread crates/data_privacy_macros_impl/CHANGELOG.md Outdated
Copilot AI review requested due to automatic review settings September 9, 2026 12:27
@ZacWalk Zac Walker (ZacWalk) changed the title chore(release): prepare 54 coordinated crate releases chore(release): prepare 50 coordinated crate releases Sep 9, 2026
Copilot AI reviewed Sep 10, 2026
View reviewed changes

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.

🔵 Needs a closer look

This is a large coordinated multi-crate release with publication-planning dependencies that requires maintainer-level release review beyond mechanical diff validation.

Review details
  • Files reviewed: 150/151 changed files
  • Comments generated: 0 new
  • Review effort level: Lite

@ZacWalk

Zac Walker (ZacWalk) commented Sep 10, 2026

Copy link
Copy Markdown
Member Author

Feedback follow-up completed in 18de2ac:

  • Fixed the uniflight keyword and the two suppressed feature-gated changelog suggestions.
  • Verified the earlier artifact fixes, reconciled the superseded multitude exclusion reply, and resolved all 27 review threads.
  • Passed local Anvil manifest sorting, all-target/all-feature Clippy, formatting, README regeneration, spelling, Cargo metadata, whitespace, and editor checks. No runtime implementation or release versions changed in this follow-up.
  • Requested final review from psandana; another eligible approval is still needed. The previous head's checks all passed, but the pushed fix has its own CI run.

The author explicitly chose to preserve performables and seismograph_cli at 0.1.0. The PR description now records that decision and the publication caveat uncovered by the focused investigation: all seven new #733 packages were absent from crates.io during the check, while the normal 58-package version-change selection excludes them. Complete their initial publication first, or verify a dependency-ordered catch-up selection in the external publisher (the local selector returns 65 using pre-#733 baseline 70bd5aa). The official pipeline publishes on main by default, so this must be confirmed before merge. No publishing was attempted and the external template's behavior has not been verified.

Final release signoff also remains necessary for the documented manual proc-macro/consumer compatibility classifications; the informational SemVer check does not replace that review.

@psandana

This comment has been minimized.

Sign in to view
@ZacWalk
fix(release): preserve main's registry lockfile resolution
f3d71c7 
Restore seven windows-sys dependency references to 0.61.2 and tempfile's getrandom reference to main's 0.3.4. Retain ring's required windows-sys 0.52 dependency and all planned workspace release versions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings September 10, 2026 20:08
@ZacWalk

Zac Walker (ZacWalk) commented Sep 10, 2026

Copy link
Copy Markdown
Member Author

Pato Sandaña (@psandana) Addressed the lockfile feedback in #739 (comment) with f3d71c7, now pushed.

  • Restored the seven windows-sys references to 0.61.2: errno, os_pipe, quinn-udp, rustix, rustls-platform-verifier, tempfile, and winapi-util.
  • Retained windows-sys 0.52.0 for ring, whose Windows ARM64 dependency explicitly requires ^0.52. Both versions are also present on main; that coexistence is intentional.
  • Restored the other registry-resolution drift in the same tempfile entry: getrandom 0.4.3 back to main's 0.3.4.
  • Verified that all 568 registry-package lock entries now exactly match target main (8624f90), and all 79 non-registry entries remain identical to the prior PR head. No package versions or planned releases changed.

An exact-version Cargo update dry run left the flexible dependency references unchanged, so the existing main selections were restored directly rather than regenerating/upgrading the dependency graph. Full locked/offline Cargo metadata confirms the corrected resolutions. Local generated Anvil Clippy (all targets/features), formatting, README regeneration, spelling, whitespace checks, and editor diagnostics passed. Fresh CI is running for the new commit.

Copilot AI reviewed Sep 10, 2026
View reviewed changes

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.

🔵 Needs a closer look

It coordinates a large multi-crate release plan with SemVer and publication-order implications that warrants final human release signoff.

Review details
  • Files reviewed: 150/151 changed files
  • Comments generated: 0 new
  • Review effort level: Lite

@ZacWalk
chore(release): merge main and preserve coordinated release versions
b1b8dc1 
Merge main at 704eba8, including compressors and the metabench support-identifier fix. Resolve the workspace dependency overlap by retaining the release versions and main's flate2 dependency. Regenerate compressors README links for bytesbuf 0.10.0.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@ZacWalk

Zac Walker (ZacWalk) commented Sep 11, 2026

Copy link
Copy Markdown
Member Author

Merged main at 704eba8 into this PR in b1b8dc1 (normal merge commit, no rebase or force-push).

  • Resolved the single Cargo.toml conflict by preserving fetch_tls 0.4.1 and both WinHTTP packages at 0.2.0, while retaining main's new flate2 dependency.
  • Preserved all 79 prior workspace package versions and the 58-package bump set. Compressors retains upstream 0.1.0; all 576 registry-package lock entries match current main, preserving the earlier Windows-resolution fix.
  • Incoming compressors and metabench macro implementation code is unchanged from main. Regenerated the compressors README for bytesbuf 0.10.0.
  • Passed 553 unit/integration tests and 26 doctests (seven existing ignored), full locked Cargo metadata, workspace Anvil Clippy, manifest sorting, formatting, README generation, spelling, whitespace, and diagnostics.
  • Updated the publication notes: the pre-feat(seismograph): introduce runtime recording #733 catch-up selector now includes compressors too (66 packages rather than the earlier 65); no publication was attempted.

GitHub now reports MERGEABLE with zero unresolved review threads. Fresh CI is running. The Vaiz and evgenyfedorov2 approvals remain recorded, but GitHub reports REVIEW_REQUIRED for the latest push; requested a refresh from Evgeny Fedorov (@evgenyfedorov2). Please review the merge update when ready.

Copilot AI reviewed Sep 11, 2026
View reviewed changes

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.

🔵 Needs a closer look

compressors needs a coordinated release or its bytesbuf 0.10.0 dependency update must be reverted.

Review details

Suppressed comments (2)

Cargo.toml:89

  • This workspace dependency update also changes compressors' normal bytesbuf dependency (crates/compressors/Cargo.toml:57-60), but compressors remains at 0.1.0 (Cargo.toml:6) and its changelog has no release entry beyond the header. That would publish the new bytesbuf 0.10.0 requirement under the old compressors version; include compressors in this coordinated release (with its changelog) or defer this workspace requirement until it is released.
bytesbuf = { path = "crates/bytesbuf", default-features = false, version = "0.10.0" }

crates/compressors/README.md:220

  • This generated README now advertises bytesbuf 0.10.0, but compressors remains at 0.1.0 (crates/compressors/Cargo.toml:6) and its changelog has no release entry. Since bytesbuf is a normal workspace dependency here (crates/compressors/Cargo.toml:59), the 58-package release plan will leave the published compressors version describing the old dependency while the repository documentation describes the new one. Either include a patch release for compressors (and its changelog) or revert this README-only regeneration.
  • Files reviewed: 151/152 changed files
  • Comments generated: 0 new
  • Review effort level: Lite

martin-kolinek
martin-kolinek previously requested changes Sep 11, 2026
View reviewed changes

@martin-kolinek martin-kolinek 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.

Showing reviewer removal.

@ZacWalk
Zac Walker (ZacWalk) enabled auto-merge (squash) September 11, 2026 11:35
@ZacWalk
Zac Walker (ZacWalk) merged commit 9794095 into main Sep 11, 2026
60 checks passed
@ZacWalk
Zac Walker (ZacWalk) deleted the release/thread-aware-core-adoption branch September 11, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot review effort, defaults to Lite
Applies to this pull request for everyone.Learn more about Copilot code review.
Copilot left review comments
@martin-kolinek martin-kolinek martin-kolinek approved these changes
@psandana Pato Sandaña (psandana) psandana approved these changes
@wukchung martinhavelka (wukchung) wukchung approved these changes
@Vaiz Evgenii (Vaiz) Vaiz approved these changes
@kate-shine Kateřina Churanová (kate-shine) kate-shine approved these changes
@evgenyfedorov2 Evgeny Fedorov (evgenyfedorov2) evgenyfedorov2 approved these changes
@martintmk martintmk martintmk approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

9 participants

@ZacWalk @psandana @martin-kolinek @wukchung @Vaiz @kate-shine @evgenyfedorov2 @martintmk