vika-cli 1.4.0

Generate TypeScript types, Zod schemas, and Fetch-based API clients from OpenAPI/Swagger specifications
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

# Setting Up Automated Versioning

This guide explains how to set up automated version bumping and changelog management.

## Recommended: cargo-release

### Setup

1. **Install cargo-release**:
   ```bash
   cargo install cargo-release
   ```

2. **Use cargo-release**:
   ```bash
   # Preview changes
   cargo release --dry-run patch
   
   # Release (bumps version, updates changelog, creates tag, pushes)
   cargo release patch  # or minor, major
   ```

3. **For automatic version detection from conventional commits**:
   Edit `.cargo-release.toml` and set:
   ```toml
   auto-version = "auto"
   ```

## Alternative: Manual Process

1. **Update version in Cargo.toml**:
   ```toml
   version = "1.0.1"
   ```

2. **Update CHANGELOG.md**:
   - Move items from `[Unreleased]` to new version section
   - Add actual changes
   - Add release date

3. **Commit and tag**:
   ```bash
   git add Cargo.toml CHANGELOG.md
   git commit -m "chore: release v1.0.1"
   git tag v1.0.1
   git push origin main --tags
   ```

## GitHub Actions (Automated Build & Release)

The `.github/workflows/release.yml` workflow:
- Triggers automatically when you push a tag (e.g., `v1.0.1`)
- Builds binaries for all platforms (Linux, macOS, Windows)
- Generates checksums for all binaries
- Creates GitHub Release with all artifacts

**Workflow**:
1. Use `cargo release patch` (or minor/major) - this creates and pushes the tag
2. GitHub Actions automatically builds binaries and creates the release

## Recommended Workflow

1. **Use cargo-release** for releases:
   ```bash
   cargo release patch
   ```

2. **GitHub Actions** automatically handles tagging and releases when you push tags