datasette-export-database 0.3a2

The datasette-export-database plugin has released version 0.3a2, addressing a significant compatibility issue that restricted the tool's functionality across different Datasette versions. This minor but important update corrects a dependency specification that had inadvertently limited plugin compatibility, expanding its usability for a broader range of Datasette installations.

The 0.3a2 release resolved a critical configuration problem in the plugin's pyproject.toml file. The previous version had pinned the Datasette dependency to an exact version (datasette==1.0a27), which prevented the plugin from functioning with any other Datasette release. Version 0.3a2 corrects this by relaxing the constraint to datasette>=1.0a27, allowing the plugin to work with version 1.0a27 and all subsequent releases. While the release notes characterize this as an "embarrassingly tiny release," the fix carries substantial practical importance for users maintaining Datasette installations on different versions.

• Improved Plugin Ecosystem Stability: Users can now upgrade their Datasette installations without being forced to abandon the datasette-export-database functionality due to version conflicts.

• Better Dependency Management: The corrected specification follows Python packaging best practices by using minimum version constraints rather than exact pinning, reducing future compatibility friction.

• Enhanced Developer Flexibility: Teams utilizing the export-database feature can maintain greater control over their Datasette versions without navigating around dependency restrictions.

• Reduced Support Burden: The fix likely eliminates confusion and support tickets arising from version incompatibility errors.

Though presented as a minor release, this update demonstrates the importance of precise dependency specification in plugin ecosystems. A single character difference—changing == to >=—restored compatibility across potentially dozens of Datasette versions. For organizations relying on datasette-export-database for data export workflows, this release removes a significant adoption barrier. The fix reinforces best practices in open-source development: dependencies should be specified as permissively as possible while maintaining stability. As Datasette continues evolving toward its 1.0 stable release, ensuring plugin compatibility across version ranges becomes increasingly critical for ecosystem health and user confidence in the platform's extensibility.