Skip to content

chore: bump to 1.10.0 - #22

Merged
KeyCode17 merged 2 commits into
mainfrom
chore/bump-1.10.0
Aug 7, 2026
Merged

chore: bump to 1.10.0#22
KeyCode17 merged 2 commits into
mainfrom
chore/bump-1.10.0

Conversation

@KeyCode17

Copy link
Copy Markdown
Owner

Why

The per-crate READMEs merged in #21 cannot reach crates.io retroactively — 1.9.0 is published and immutable. release.yml gates the crates.io publish on minor/major/initial, so a patch tag would create a GitHub release and publish nothing. This is the minor that carries the docs to the registry.

No code change from v1.9.0. Version, dependency pins, README status line, and one build-tooling fix.

Contents

  • [workspace.package] version1.10.0, and all 16 internal pxsolver-* pins moved with it — done by cargo xtask bump minor, exercising the re-pin fix from feat(proxy): honour the per-request egress proxy end to end #20 for the first time.
  • .cargo/config.toml added. ADR-0016, the root README and xtask/README.md all document cargo xtask <cmd>, but no alias file existed, so every documented invocation failed with error: no such command: xtask. Contributors had to know to run cargo run -p xtask -- instead.
  • README status line updated.

After merge

Tag v1.10.0 on the merge commit. release.yml then publishes all 16 crates with their READMEs attached, since the tagged commit is on main and the bump kind is minor.

Verification

cargo fmt --check · clippy clean under the unwrap/expect/panic ban · full test suite green · 200-LOC gate green · cargo xtask bump minor --local ran the build+test gate itself before committing.

ADR-0016, the root README and xtask's own README all invoke `cargo xtask
<cmd>`, but no .cargo/config.toml existed, so the alias resolved to
nothing and every documented invocation failed with "no such command".
Contributors had to know to run `cargo run -p xtask --` instead.
@KeyCode17
KeyCode17 merged commit 6cadc98 into main Aug 7, 2026
6 checks passed
@KeyCode17
KeyCode17 deleted the chore/bump-1.10.0 branch August 7, 2026 17:56
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.

1 participant