agentport 0.1.0

A unified TUI installer for AI agent skills and plugins
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

# Releasing Agentport

Releases are published to crates.io from GitHub Actions when a `v<version>` tag is pushed.

## One-time repository setup

1. Sign in to crates.io, verify your email, and confirm that `agentport` is available.
2. Create a crates.io API token scoped to publishing `agentport` when available.
3. In GitHub, add the token as the repository secret `CARGO_REGISTRY_TOKEN`. The publish job maps this secret to Cargo's standard environment variable of the same name.
4. The workflow uses a `crates-io` deployment environment; configure required reviewers for it if desired.

## Release checklist

1. Update `version` in `Cargo.toml` and run `cargo update -w` if the lockfile needs refreshing.
2. Move entries from `Unreleased` into a dated version in `CHANGELOG.md` and update its comparison links.
3. Run:

   ```sh
   cargo fmt --all -- --check
   cargo clippy --all-targets --all-features -- -D warnings
   cargo test --all-targets --all-features
   cargo publish --dry-run --locked
   ```

4. Commit the release changes and push them to `main`.
5. Create and push the matching annotated tag:

   ```sh
   git tag -a v0.1.0 -m "Agentport 0.1.0"
   git push origin v0.1.0
   ```

The publish workflow verifies that the tag matches `Cargo.toml`, reruns release checks, and publishes exactly once. crates.io versions are permanent and cannot be overwritten.