# GitCaddy Vault Compatibility

## Version Compatibility Matrix

| Vault Version | Server Version | Notes |
|---------------|----------------|-------|
| v1.0.4        | v3.0.6+        | Solo tier with limited versioning/CI-CD |
| v1.0.3        | v3.0.6+        | Build failed - use v1.0.4 |
| v1.0.2        | v3.0.5         | Initial public release |

## Important Notes

### Go Plugin Versioning

GitCaddy Vault is distributed as a Go plugin (`.so` file). Go plugins require **exact package version matching** between the plugin and the host application.

This means:
- Each vault release is built against a specific server version
- A vault plugin built for server v3.0.5 will **not** load on server v3.0.6
- Always use the vault version that matches your server version

### Automatic Rebuilds

When a new server version is released, the vault is automatically rebuilt:

1. Server CI tags a new release (e.g., `v3.0.7`)
2. Server CI triggers a repository dispatch to the vault repo
3. Vault CI updates its server dependency and tags a new release (e.g., `v1.0.5`)
4. Vault CI builds and uploads the new `.so` files

### Finding the Right Version

To find which vault version to use:

1. Check your server version: `gitea --version`
2. Find the matching vault release in this compatibility matrix
3. Download the vault `.so` for your platform from the release

### Upgrading

When upgrading the server:

1. Stop the server
2. Replace the server binary
3. Download the matching vault plugin version
4. Replace the vault `.so` in your plugins directory
5. Start the server

Both server and vault must be upgraded together.