Limited

Files

logikonline 482ba65b2d feat: add automated rebuild on server release

- Add server-release.yml workflow that listens for repository_dispatch
- Auto-bumps vault version and rebuilds when server is tagged
- Add COMPATIBILITY.md documenting version requirements

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-17 12:36:36 -05:00

1.6 KiB

Raw Blame History

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:

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

Finding the Right Version

To find which vault version to use:

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

Upgrading

When upgrading the server:

Stop the server
Replace the server binary
Download the matching vault plugin version
Replace the vault .so in your plugins directory
Start the server

Both server and vault must be upgraded together.

1.6 KiB Raw Blame History