Skip to content

Commit 9c7d4d7

Browse files
committed
refactor(rust): move crate under crates and add release guide
1 parent d7be45e commit 9c7d4d7

32 files changed

Lines changed: 50 additions & 1 deletion

crates/tanstack-ai/release.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# tanstack-ai release process
2+
3+
This document describes how to publish the Rust crate to crates.io.
4+
5+
## Prerequisites
6+
7+
- crates.io owner access for `tanstack-ai`
8+
- `cargo` authenticated (`cargo login <TOKEN>`), or `CARGO_REGISTRY_TOKEN` set
9+
- all intended changes merged to `main`
10+
11+
## 1) Bump version
12+
13+
Update `version` in `crates/tanstack-ai/Cargo.toml`.
14+
15+
## 2) Validate locally
16+
17+
From repo root:
18+
19+
```bash
20+
cargo test --manifest-path crates/tanstack-ai/Cargo.toml
21+
cargo package --manifest-path crates/tanstack-ai/Cargo.toml
22+
```
23+
24+
`cargo package` verifies the crate can be built from the published archive.
25+
26+
## 3) Publish
27+
28+
From repo root:
29+
30+
```bash
31+
cargo publish --manifest-path crates/tanstack-ai/Cargo.toml
32+
```
33+
34+
If needed, publish with an explicit token:
35+
36+
```bash
37+
CARGO_REGISTRY_TOKEN=<token> cargo publish --manifest-path crates/tanstack-ai/Cargo.toml
38+
```
39+
40+
## 4) Tag and notes
41+
42+
Create a git tag after publish, for example:
43+
44+
```bash
45+
git tag rust/tanstack-ai-v0.1.0
46+
git push origin rust/tanstack-ai-v0.1.0
47+
```
48+
49+
Then document highlights in the GitHub release notes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

packages/rust/tanstack-ai/src/client/connection_adapters.rs renamed to crates/tanstack-ai/src/client/connection_adapters.rs

File renamed without changes.

0 commit comments

Comments
 (0)