Skip to content

v1.10.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Aug 17:57
· 4 commits to main since this release
v1.10.0
6cadc98
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.10.0 — Per-crate documentation on crates.io

No code change from v1.9.0. This release exists to carry documentation to the registry: crates.io renders each crate's own README, versions are immutable, and the publish is gated on a minor bump — so the READMEs added after v1.9.0 needed a version of their own to become visible.

What's new

  • A README for all 19 workspace members. Each published crate's page now shows its purpose, an install snippet, its public surface, and the caveats specific to it — proxy credentials for pxsolver-harvester, the rotation math for pxsolver-camoufox, stub status for pxsolver-turnstile / pxsolver-captcha / pxsolver-datadome, and the v1.9.0 signature change for pxsolver-pipeline. Before this, all 16 pages showed a one-line description and nothing else.
  • The package/crate name split is documented. You depend on pxsolver-core but you use px_core::…. The pxsolver- prefix namespaces the family on crates.io; the source-level name stays short. This was not discoverable from a crates.io page.
  • .cargo/config.toml added, wiring up the cargo xtask alias. ADR-0016, the root README and xtask/README.md all documented cargo xtask <cmd>, but no alias file existed — every documented invocation failed with error: no such command: xtask.

Corrected

The root README told readers to run cargo install pxsolver-server pxsolver-cli. Both binaries are publish = false and have never been on crates.io, so that command has never worked. Only the 16 library crates are published; the binaries build from source:

git clone https://github.com/KeyCode17/px-solver
cd px-solver
cargo build --release -p px-server -p px-cli

Upgrading from v1.9.0

Nothing to do — the code is identical. If you are coming from v1.8.0 or earlier, note that v1.9.0 was source-breaking: ChallengeHandler::solve and SolveDispatcher::solve take a SolveAction / SolveRequest instead of &PageHtml / &str. See the v1.9.0 notes.

Verification

cargo fmt --check · clippy clean under the unwrap/expect/panic ban · full test suite green · 200-LOC gate green · all 16 crates published at 1.10.0 with readme_path populated.

PRs merged: #21 (per-crate READMEs), #22 (bump + xtask alias).

Assets 2
Loading