-
Notifications
You must be signed in to change notification settings - Fork 0
Support Policy
LakeDB is independently maintained and community support is provided on a best-effort basis without a contractual SLA.
- The latest published build receives bug, compatibility and security fixes.
- The active beta or release candidate is supported while it is the path to the next stable build.
- Older lines remain documented but are not actively supported.
- After 1.0, fixes target the latest stable release instead of several long-lived branches.
The Releases page retains up to two packaged builds from the current version line and the newest packaged build from the previous available line. Historical tags can remain after their installers are removed.
- Ask workflow questions in Q&A.
- Propose features in Ideas.
- Report reproducible defects with the bug form.
- Report vulnerabilities through the private process described in Security.
Use Help → Report a problem inside LakeDB to open the bug form. If the local diagnostics are useful, open View → Diagnostics, copy the support report and review it before pasting. LakeDB never submits that report automatically.
Include the LakeDB version, operating system, database product/version, expected result and observed result. Remove credentials, customer information, internal hosts and sensitive SQL before posting.
See the canonical SUPPORT.md.
- Connections, SSL and SSH
- SQL Editor
- Tables and Safe Editing
- Backup, Import and Migrations
- Appearance, Language and Sessions
- Updates, Recovery and Restores
- Community, Ideas and Requests
- Security and Privacy
- Privacy
- Security Policy
- Support Policy
- Compatibility
- Troubleshooting
- Frequently Asked Questions
- Roadmap to 1.0
- Version History