Skip to content

release: 0.2.6 (docs.rs fix + README table reordering)#36

Merged
kingchenc merged 3 commits into
mainfrom
release/0.2.6
May 24, 2026
Merged

release: 0.2.6 (docs.rs fix + README table reordering)#36
kingchenc merged 3 commits into
mainfrom
release/0.2.6

Conversation

@kingchenc
Copy link
Copy Markdown
Owner

Summary

Three commits land together for the 0.2.6 patch:

  • fix(docs-rs)doc_auto_cfg was removed in Rust 1.92 and merged into doc_cfg (Implement RFC 3631: add rustdoc doc_cfg features rust-lang/rust#138907). docs.rs builds against the latest nightly with --cfg docsrs, so every published 0.2.x tripped E0557 on the #![cfg_attr(docsrs, feature(doc_auto_cfg))] lines in wickra, wickra-core, wickra-data. Stable rustc never enables that cfg, so GitHub CI couldn't see it. All three crates now gate on doc_cfg (same rendered output, builds again on nightly).

  • docs(readme) — Wickra is now the first row of every comparison table across the umbrella + binding READMEs (with a ★ marker), instead of the last. Same column data, same winner annotations, just the pivot row in the position a reader actually wants it.

  • release: bump — workspace, every binding (Python, Node, 5 platform stubs), the release.yml comment, and the CHANGELOG all move from 0.2.5 → 0.2.6. wickra-win32-arm64-msvc stays excluded with the same npm-spam-filter rationale.

Test plan

  • cargo fmt --all --check
  • cargo clippy --workspace --all-targets --all-features -- -D warnings
  • cargo test --workspace --all-features — every crate green
  • grep "0\.2\.5" shows only the historical CHANGELOG entries + one historical "Since 0.2.5, BinanceConfig" doc-line
  • CI matrix passes on the bump branch
  • After merge + v0.2.6 tag push: docs.rs successfully builds 0.2.6 (the whole reason for this PR)

kingchenc added 3 commits May 24, 2026 03:10
`doc_auto_cfg` was removed in Rust 1.92.0 and folded back into
`doc_cfg` (rust-lang/rust#138907). docs.rs builds with the latest
nightly and sets `--cfg docsrs`, so the previous

    #![cfg_attr(docsrs, feature(doc_auto_cfg))]

aborts compilation with E0557 on every published 0.2.x. GitHub CI
never tripped this — stable rustc ignores the line because nothing
sets the `docsrs` cfg there.

Switch all three published library crates (`wickra`, `wickra-core`,
`wickra-data`) to the merged-into `doc_cfg` gate. Same intent, same
on-docs.rs output, builds again on nightly.
Reorders the "Why Wickra exists" library-comparison table and the two
benchmark headers so Wickra is the first row (with a ★ marker) instead
of the last. The previous order placed Wickra at the bottom, which
buries the only row a reader landing on the README is here to compare
against. Same column data, same ★/winner annotations, just the row
order flipped and a ★ prefix on the Wickra label.

Mirrored across the umbrella README and every binding README so the
crates.io / PyPI / npm landing pages stay in sync.
Workspace, every binding (Python, Node, Node platform stubs), the
release.yml comment and the CHANGELOG all move together to 0.2.6 so
the next tagged release lines every artefact up.

0.2.6 carries two changes from the [0.2.6] CHANGELOG entry:
- fix(docs-rs): swap the now-removed `doc_auto_cfg` feature gate for
  the merged-into `doc_cfg` so docs.rs nightly builds resume.
- docs(readme): float ★ Wickra to the top of every comparison table
  across the umbrella + binding READMEs.

wickra-win32-arm64-msvc stays excluded for this release with the same
npm spam-filter rationale that held for 0.2.5.
@codecov
Copy link
Copy Markdown

codecov Bot commented May 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@kingchenc kingchenc merged commit 070be2e into main May 24, 2026
28 checks passed
@kingchenc kingchenc deleted the release/0.2.6 branch May 24, 2026 01:20
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