Skip to content

chore(release): preview changed package release plan - #669

Draft
martintmk wants to merge 3 commits into
user/martintomka/20260812-release-agentic-skillfrom
user/martintomka/20260813-release-simulation
Draft

martintmk wants to merge 3 commits into
user/martintomka/20260812-release-agentic-skillfrom
user/martintomka/20260813-release-simulation

Conversation

@martintmk

@martintmk martintmk commented Aug 13, 2026

Copy link
Copy Markdown
Member

Important

This is a release simulation only generated by the release skill from PR #662. Do not merge this PR to publish packages. No packages have been published.

Purpose

Dogfood the changed-package workflow against the current Oxidizer history so reviewers can inspect classifications, dependency cascades, exact version targets, changelogs, and generated READMEs while the release skill is being refined.

Result

  • Mode: changed
  • Direct releases: 16
  • Cascade releases: 21
  • Total releases: 37
  • Warnings: 0
  • Consensus: unanimous GPT + Claude review after one blocking refinement pass
  • Post-merge correction: PR fix(release): cascade exposed dependency breaks #646 crate-root exposure handling raises templated_uri_macros_impl and templated_uri_macros from 0.4.1 patch previews to 0.5.0 breaking previews.

Note

Codecov reports 100% patch coverage: all modified and coverable lines are covered. Its project check compares the stacked base's path-filtered 100% result with a broader 97% workspace run, so that project-level failure is not actionable through tests in this source-free simulation.

Version plan

Package From To Change Source Manual review
data_privacy_core 0.1.2 0.1.3 patch user no
data_privacy_macros_impl 0.10.3 0.11.0 breaking user no
fetch_options 0.2.3 0.2.4 patch user no
http_path_template 0.2.0 0.2.1 patch user no
internity 0.1.0 0.1.1 nonbreaking user no
ohno_macros 0.4.0 0.5.0 breaking user yes
thread_aware_macros_impl 0.7.4 0.8.0 breaking user no
data_privacy_macros 0.10.3 0.11.0 breaking user yes
ohno 0.4.0 0.5.0 breaking user no
routerama_build 0.1.0 0.1.1 patch user no
thread_aware_macros 0.7.5 0.8.0 breaking user yes
cachet_tier 0.3.0 0.4.0 breaking cascade no
data_privacy 0.12.4 0.13.0 breaking cascade no
fetch_tls 0.3.0 0.4.0 breaking cascade no
routerama_macros 0.1.0 0.1.1 patch user yes
templated_uri_macros_impl 0.4.0 0.5.0 breaking cascade no
thread_aware 0.9.0 0.10.0 breaking cascade no
anyspawn 0.7.0 0.8.0 breaking cascade no
bytesbuf 0.8.0 0.9.0 breaking cascade no
cachet_memory 0.6.0 0.7.0 breaking cascade no
cachet_service 0.3.0 0.4.0 breaking cascade no
routerama 0.1.0 0.1.1 patch user no
templated_uri_macros 0.4.0 0.5.0 breaking cascade yes
tick 0.5.0 0.6.0 breaking user no
uniflight 0.4.0 0.5.0 breaking cascade no
anyspawn_azure 0.2.0 0.3.0 breaking cascade no
bytesbuf_io 0.8.0 0.9.0 breaking cascade no
cachet 0.11.0 0.12.0 breaking cascade no
multitude 0.8.0 0.9.0 breaking user no
rest_over_grpc 0.2.0 0.2.1 patch cascade no
seatbelt 0.7.0 0.8.0 breaking cascade no
templated_uri 0.4.0 0.5.0 breaking cascade no
http_extensions 0.9.0 0.10.0 breaking user no
fetch_hyper 0.6.0 0.7.0 breaking cascade no
seatbelt_http 0.7.0 0.8.0 breaking cascade no
fetch 0.15.0 0.16.0 breaking cascade no
fetch_azure 0.5.0 0.6.0 breaking cascade no

Classification highlights

  • thread_aware_macros_impl and data_privacy_macros_impl: breaking because public APIs expose syn types across the workspace syn 2 to syn 3 upgrade.
  • ohno_macros: breaking because previously accepted #[no_constructors] input now fails compilation.
  • tick and internity: nonbreaking public API additions missed by objective tooling.
  • Renamed crate roots and indirect public re-exports participate in breaking cascades; this corrected the templated URI macro line.
  • Packaged broken-link repairs are patch changes; opaque generated README metadata alone does not seed a release.

Validation

  • cargo-semver-checks 0.48.0 completed for all 20 modified ordinary libraries.
  • Atomic application completed successfully, including changelog generation, README regeneration, Cargo validation, exact-version verification, and rollback safeguards.
  • The corrected plan contains 37 normalized tuples and zero warnings; all manifest versions were verified against it.

AI-generated release simulation for review.

Apply the release skill's consensus-verified 37-package changed-mode plan for review only; this commit does not publish packages.

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

Copilot-Session: f77d7bd4-9f62-45e2-8805-5ead9000f286
@codecov

codecov Bot commented Aug 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.0%. Comparing base (29a6d8a) to head (4ef7833).

❌ Your project check has failed because the head coverage (97.0%) is below the target coverage (100.0%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@                                Coverage Diff                                @@
##           user/martintomka/20260812-release-agentic-skill    #669     +/-   ##
=================================================================================
- Coverage                                            100.0%   97.0%   -3.0%     
=================================================================================
  Files                                                  503     497      -6     
  Lines                                                57407   55074   -2333     
=================================================================================
- Hits                                                 57407   53474   -3933     
- Misses                                                   0    1600   +1600     
Flag Coverage Δ
linux 97.0% <ø> (?)
linux-arm 97.0% <ø> (?)
windows 97.1% <ø> (?)

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.

Stack the review-only release preview on the latest release-skill branch, including the upstream exposed-dependency cascade fixes.

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

Copilot-Session: f77d7bd4-9f62-45e2-8805-5ead9000f286
Apply the unified resolver's renamed-root exposure evidence: the ohno break propagates through templated_uri_macros_impl and templated_uri_macros as 0.5.0 breaking releases.

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

Copilot-Session: f77d7bd4-9f62-45e2-8805-5ead9000f286
@martintmk martintmk added the agency-rocket Touched by a rocket skill label Aug 13, 2026
@@ -1,5 +1,11 @@
# Changelog

## [0.5.0] - 2026-08-13

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Suggested change
## [0.5.0] - 2026-08-13
## [0.4.1] - 2026-08-13

even though the syn was uprgraded to version 3, form SemVer perspective there were no breaking changes. I believe when it to comes to macros, the skill must be little bit more careful when evaluating what is breaking change.

@martintmk

Copy link
Copy Markdown
Member Author

review this PR

@martintmk martintmk left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Posted by an AI agent

Three release-artifact issues were found: two blocking changelog correctness problems and one non-blocking structure issue.

Coverage included the exact 104-file diff and all 37 paired package manifests, public APIs and docs, tests, performance, naming, telemetry, resilience, and consistency. No runtime or public API behavior changed; cargo metadata, targeted cargo check, and git diff --check passed.

Comment thread crates/tick/CHANGELOG.md

- ✨ Features

- add configurable fast instant retrieval ([#648](https://github.com/microsoft/oxidizer/648))

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Posted by an AI agent

Generated changelog references use invalid GitHub paths

Problem
All 52 PR references newly added across 23 changelogs omit the /pull/ segment; for example, this link targets https://github.com/microsoft/oxidizer/648, which returns 404 instead of opening PR #648.

Why this matters
Every source link in these generated release notes is broken, so consumers cannot trace the changes being published.

Suggested fix
Restore /pull/ in the release generator's changelog link template and regenerate the affected changelogs.


- ✨ Features

- add REST transcoding for gRPC services ([#600](https://github.com/microsoft/oxidizer/600))

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Posted by an AI agent

Release notes attribute unrelated changes to these packages

Problem
This entry attributes REST transcoding from PR #600 to data_privacy_core, but that PR changed only this crate's generated README links. The same false attribution appears in data_privacy_macros_impl, which also credits PR #585 even though its only package change was manifest array formatting.

Why this matters
The published changelogs would claim functionality that these packages did not gain, misleading consumers about the contents of the release.

Suggested fix
Exclude generated README-only and non-semantic formatting changes from package attribution, then regenerate the affected changelogs.


- export frozen readers and guarantee dense handles ([#657](https://github.com/microsoft/oxidizer/657))

All notable changes to this crate are documented here. The format is based on

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Posted by an AI agent · Non-blocking

Changelog preamble is nested inside a released section

Problem
The Keep a Changelog/Semantic Versioning preamble was moved below the new 0.1.1 entries, making it part of that released section. The same relocation occurs in http_path_template and rest_over_grpc.

Why this matters
The document structure now presents repository boilerplate as release content and makes the generated changelogs harder to interpret.

Suggested fix
Treat the preamble as file header text and regenerate these changelogs with it before the first version heading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agency-rocket Touched by a rocket skill

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant