rustuse 0.1.2

Unified facade crate for the published RustUse sets and child crates
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

# Releasing

RustUse/rustuse releases are cut from the canonical GitHub repository.

## Release flow

1. Ensure CI, publish-readiness, and security workflows are green on `main`.
2. Let `release-plz` open or update the release PR.
3. Review the generated version bump and release notes for accuracy.
4. Merge the release PR from the canonical repository.
5. Let the release workflow publish the crate from GitHub.

## Pre-release checks

Run the local readiness path before merging release-affecting changes:

```sh
cargo xcheck
cargo xexamples
cargo xtest-minimal
cargo publish --dry-run --allow-dirty -p rustuse
```

## Notes

- `rustuse` is a facade crate, so releases should stay aligned with the
  currently published child crates and feature wiring.
- Mirror CI is validation only. Tags, GitHub releases, and crates.io publishes
  are created from the canonical GitHub repository.
- `rustuse` `0.1.0` has already been published, so follow-up releases should
  use the checked-in `release-plz` automation rather than a first-publish
  bootstrap path.
- Published crates.io versions are permanent. Verify crate metadata, README
  examples, and changelog entries before any real publish.