github-to-sqlite 2.9.1 fixes compatibility with sqlite-utils 4.x

github-to-sqlite is a utility that exports GitHub data, such as issues, pull requests, or repository metadata, into a SQLite database. This release, 2.9.1, does not add new functionality but resolves a compatibility problem with sqlite-utils 4.x, a separate library used for SQLite database operations. The issue likely stemmed from changes in sqlite-utils' API or behavior that github-to-sqlite relied on, causing failures when the two were used together.

For engineers, the cost of adoption is minimal. The update requires no changes to existing scripts or database schemas. The fix is isolated to the interaction between github-to-sqlite and sqlite-utils, meaning users can upgrade without worrying about downstream effects on their data or workflows. However, the update only addresses compatibility with sqlite-utils 4.x; older versions of sqlite-utils may still work but are not explicitly supported in this release.

The scope of the fix is narrow. It does not expand the tool’s capabilities or improve performance, nor does it address other potential dependency conflicts. If you are not using sqlite-utils 4.x, this update may not be immediately relevant. The release also does not introduce backward-incompatible changes, so users can safely upgrade without testing for regressions in unrelated functionality.

This update highlights the fragility of dependency chains in data tooling. A minor version bump in sqlite-utils broke a downstream tool, demonstrating how even small changes in utility libraries can disrupt workflows. For maintainers, it underscores the importance of pinning dependencies or testing against multiple versions of critical libraries to avoid silent failures in production environments.