Bump drizzle-kit from 0.19.13 to 0.20.7

[dependabot]

Bumps drizzle-kit from 0.19.13 to 0.20.7.

Release notes

Sourced from drizzle-kit's releases.

0.20.7

Bug fixes

• BUG drizzle-kit introspect:mysql from Planetscale db returns wrong primary key #216
• BUG: v0.20.2 push:mysql error: there can be only one auto column and it must be defined as a key #234
• Fixed dropping all primary keys and creating them 1 more time

Improvements

• Check names for indexes and notify if you have specified the same index names within the schema.
• Verify that auto-increment can only be created for primary keys in MySQL

0.20.0

Drizzle ORM version 0.29.0 will require a minimum Drizzle Kit version of 0.20.0, and vice versa. Therefore, when upgrading to a newer version of Drizzle ORM, you will also need to upgrade Drizzle Kit. This may result in some breaking changes throughout the versions, especially if you need to upgrade Drizzle Kit and your Drizzle ORM version is older than <0.28.0

New Features

New way to define drizzle.config using defineConfig function

import { defineConfig } from 'drizzle-kit'
export default defineConfig({
schema: "./schema.ts",
out: "./drizzle",
driver: "..",
dbCredentials: {
// connection
},
verbose: true,
strict: true,
})

Possibility to access Cloudflare D1 with Drizzle Studio using wrangler.toml file

You can now use Drizzle Studio with your D1 database. Please note that it may be slow at times because Drizzle Studio utilizes Wrangler CLI calls to perform data selection, updates, deletions, and insertions. The speed of these operations depends on the performance of Wrangler CLI calls.

To use Drizzle Studio with the D1 database, you need to provide the file path to your wrangler.toml file and specify the dbName you are using in Cloudflare D1

import { defineConfig } from 'drizzle-kit'
export default defineConfig({
schema: "./schema.ts",
out: "./drizzle",
driver: "d1",
dbCredentials: {
wranglerConfigPath: 'wrangler.toml',
dbName: 'd1-test'
},
</tr></table>

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #32.