Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrading sqlite3 to 5.1.4 #216

merged 1 commit into from Dec 22, 2022

upgrading sqlite3 to 5.1.4 #216

merged 1 commit into from Dec 22, 2022


Copy link

@jaredwray jaredwray commented Dec 22, 2022

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
upgrading sqlite3 to 5.1.4

Copy link

codecov bot commented Dec 22, 2022

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (27602d5) compared to base (289d651).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #216   +/-   ##
  Coverage   100.00%   100.00%           
  Files            2         2           
  Lines          161       161           
  Branches        38        38           
  Hits           161       161           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@jaredwray jaredwray merged commit 4486808 into main Dec 22, 2022
7 checks passed
@jaredwray jaredwray deleted the upgrading-sqlite3-to-5.1.4 branch December 22, 2022 22:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant