⚠️ Important: Fresh Start Required
This release removes the automated migration from v2.x to v3.0. Users upgrading from v2.x must start fresh with a new data volume.
What's Changed
- 🚫 Removed automated v2→v3 migration - Migration was causing issues due to fundamental architectural changes between versions
- 📝 Added clear upgrade documentation - New
UPGRADE.md
explains the fresh start requirement - 🧹 Cleaned up Docker entrypoint - Removed complex migration logic for simpler, more reliable startup
- 📚 Updated README - Points users to upgrade guide and clarifies v3 requirements
Upgrade Instructions
If upgrading from v2.x:
- Stop your v2 container
- Create a new volume for v3
- Start v3 with the new volume
- Re-configure your GitHub and Gitea connections
See UPGRADE.md for detailed instructions.
Why No Migration?
v3.0 introduces fundamental changes:
- New authentication system (Better Auth)
- Encrypted token storage
- Different database schema
- SSO and OIDC support
These changes make automated migration complex and error-prone. A fresh start ensures the best v3 experience.
Full Changelog: v3.0.0...v3.0.1