gvsn 1.0.1

A fast, cross-platform Go version manager written in Rust
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

## Summary

<!-- One or two sentences on what this PR changes and why. -->

## Type of change

- [ ] Bug fix
- [ ] New feature
- [ ] Refactor / code quality
- [ ] Documentation
- [ ] CI / build
- [ ] Security fix
- [ ] Breaking change

## Checklist

### Code quality

- [ ] `cargo fmt --all` passes locally
- [ ] `cargo clippy --all-targets --all-features -- -D warnings` passes locally
- [ ] `cargo test --all-targets` passes locally (Linux + Windows if possible)
- [ ] No `unwrap()` / `expect()` in production paths - errors are propagated with `anyhow`
- [ ] No `unsafe` blocks (or justified with a comment if unavoidable)

### Shell integration

- [ ] If shell profile injection changed: verified idempotency (re-running `gvsn setup` is safe)
- [ ] If `inject_profile` / `remove_gvsn_lines` changed: existing tests updated
- [ ] If a new shell is added: all four implementations (bash, zsh, fish, powershell) updated

### Release impact

- [ ] Commit message follows [Conventional Commits](https://www.conventionalcommits.org/) so auto-versioning works correctly
  - `feat:` → minor bump, `fix:`/`perf:` → patch bump, `feat!:` → major bump
- [ ] If `upgrade.rs` or artifact naming changed: `release_binary_name()` updated to match

### Security

- [ ] No secrets, credentials, or API keys committed
- [ ] No new network calls without timeout handling
- [ ] External input (user args, file paths) is validated at the boundary

## Testing notes

<!-- Describe how you tested this. Which OS(es)? Manual steps? Edge cases covered? -->

## Related issues

<!-- Closes #... -->