chore(deps): update dependency @types/knex to ^0.16.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/knex	^0.15.1 -> ^0.16.0

---

Release Notes

tgriesser/knex (@​types/knex)

v0.16.1

Compare Source

Breaking Changes:

• Use datetime2 for MSSQL datetime + timestamp types. This change is incompatible with MSSQL older than 2008 #​2757
• Knex.VERSION() method was removed, run "require('knex/package').version" instead #​2776
• Knex transpilation now targets Node.js 6, meaning it will no longer run on older Node.js versions #​2813
• Add json type support for SQLite 3.9+ (tested to work with Node package 'sqlite3' 4.0.2+) #​2814

New features:

• Support passing explicit connection to query builder (#​2817)
• Introduced abstraction for getting migrations to make migration bundling easier #​2775
• Allow timestamp with timezone on mssql databases #​2724
• Allow specifying multiple migration directories #​2735
• Allow cloning query builder with .userParams({}) assigned to it #​2802
• Allow chaining of increment, decrement, and update #​2740
• Allow table names with forUpdate/forShare #​2834
• Added whereColumn and the associated not / and / or methods for using columns on the right side of a where clause #​2837
• Added whereRecursive method to make self-referential CTEs possible #​2889
• Added support for named unique, primary and foreign keys to SQLite3 #​2840
• Added support for generating new migration and seed files without knexfile #​2884 #​2905 #​2935
• Added support for multiple columns in .orderBy() #​2881
• Added option of existingType to .enum() method to support repeated use of enums #​2719
• Added option to pass indexType for MySQL dialect #​2890
• Added onVal and the associated not / and / or methods for using values in on clauses within joins #​2746
• Kill queries after timeout for PostgreSQL #​2636
• Manage TypeScript types internally #​2845
• Support 5.0.0+ versions of mssql driver #​2861
• Typescript migration stub #​2816
• Options object for passing timestamp parameters + regression tests #​2919

Bug fixes:

• Implement fail-fast logic for dialect resolution #​2776
• Fixed identifier wrapping for using(). Use columnize instead of wrap in using() #​2713
• Fix issues with warnPromise when migration does not return a promise #​2730
• Compile with before update so that bindings are put in correct order #​2733
• Fix join using builder withSchema #​2744
• Throw instead of process.exit when client module missing #​2843
• Display correct filename of a migration that failed #​2910
• Fixed support of knexSnakeCaseWrappers in migrations #​2914
• SQlite3 renameColunm quote fix #​2833
• Adjust typing for forUpdate()/forShare() variant with table names #​2858
• Fix execution of Oracle tests on Node 11 #​2920
• Fix failures in oracle test bench and added it back to mandatory CI tests #​2924
• Knex client knexfile resolution fix #​2923
• Add queryContext to type declarations #​2931

Test / internal changes:

• Add tests for multiple union arguments with callbacks and builders #​2749
• Update dependencies #​2772 #​2810 #​2842 #​2848 #​2893 #​2904
• Separate migration generator #​2786
• Do not postprocess internal queries in Migrator #​2914 #​2934
• Use Babel 7 #​2813
• Introduce LGTM.com badge #​2755
• Cleanup based on analysis by https://lgtm.com #​2870
• Add test for retrieving null dates #​2865
• Add link to wiki #​2866
• Add tests for specifying explicit pg version #​2895
• Execute tests on Node.js 11 #​2873
• Version upgrade guide #​2894

---

Configuration

📅 Schedule: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.