-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix(deps): update dependency drizzle-kit to ^0.21.1 #462
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
homarr-renovate
bot
force-pushed
the
renovate/drizzle-kit-0.x
branch
from
May 9, 2024 19:48
cdf344d
to
076e1e5
Compare
homarr-renovate
bot
changed the title
fix(deps): update dependency drizzle-kit to ^0.21.0
fix(deps): update dependency drizzle-kit to ^0.21.1
May 10, 2024
homarr-renovate
bot
force-pushed
the
renovate/drizzle-kit-0.x
branch
from
May 10, 2024 16:30
076e1e5
to
1c055f2
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Meierschlumpf
previously approved these changes
May 10, 2024
ajnart
reviewed
May 10, 2024
Meierschlumpf
approved these changes
May 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.20.18
->^0.21.1
Release Notes
drizzle-team/drizzle-kit-mirror (drizzle-kit)
v0.21.1
Compare Source
Drizzle Studio support for per-database preferences
When connecting to different databases with Drizzle Local Studio, we will store all preferences such as selected tabs, hidden columns, pagination, etc., separately for each database
Drizzle Studio support for advanced bug report context
Now you can assist us in debugging Drizzle Studio errors. No more need to say, "Please share your schema with us"; just click a button, download the bug report, and send it to us!
v0.21.0
Compare Source
Breaking changes
❗ Snapshots Upgrade
All PostgreSQL and SQLite-generated snapshots will be upgraded to version 6. You will be prompted to upgrade them by running
drizzle-kit up
❗ Removing :dialect from
drizzle-kit
cli commandsYou can now just use commands, like:
drizzle-kit generate
drizzle-kit push
without specifying dialect. This param is moved to
drizzle.config.ts
❗
drizzle.config
updatedialect
is now mandatory; specify which database dialect you are connecting to. Options includemysql
,postgresql
, orsqlite
.driver
has become optional and will have a specific driver, each with a different configuration ofdbCredentials
. Available drivers are:aws-data-api
turso
d1-http
- currently WIPexpo
url
- a unified parameter for the previously existingconnectionString
anduri
.migrations
- a new object parameter to specify a custom table and schema for the migrate command:table
- the custom table where drizzle will store migrations.schema
- the custom schema where drizzle will store migrations (Postgres only).Usage examples for all new and updated commands
Drizzle driver selection follows the current strategy:
If a
driver
is specified, use this driver for querying.If no driver is specified:
For
postgresql
dialect, Drizzle will:pg
driver is installed and use it.postgres
driver and use it.@vercel/postgres
.@neondatabase/serverless
.For
mysql
dialect, Drizzle will:mysql2
driver is installed and use it.@planetscale/database
and use it.For
sqlite
dialect, Drizzle will:@libsql/client
driver is installed and use it.better-sqlite3
and use it.❗ MySQL schemas/database are no longer supported by drizzle-kit
Drizzle Kit won't handle any schema changes for additional schemas/databases in your drizzle schema file
New Features
🎉 Pull relations
Drizzle will now pull
relations
from the database by extracting foreign key information and translating it into arelations
object. You can view therelations.ts
file in theout
folder after introspection is completeFor more info about relations, please check the docs
🎉 Custom name for generated migrations
To specify a name for your migration you should use
--name <name>
Usage
🎉 New command
migrate
You can now apply generated migrations to your database directly from
drizzle-kit
Usage
By default, drizzle-kit will store migration data entries in the
__drizzle_migrations
table and, in the case of PostgreSQL, in adrizzle
schema. If you want to change this, you will need to specify the modifications indrizzle.config.ts
.How to migrate from
0.20.18
to0.21.0
1. Remove all
:dialect
prefixes from your Drizzle-Kit commands.Example: Change
drizzle-kit push:mysql
todrizzle-kit push
.2. Update your
drizzle.config.ts
file:dialect
todrizzle.config.ts
. It is now mandatory and can be 'postgresql', 'mysql', or 'sqlite'.driver
todrizzle.config.ts
ONLY if you are usingaws-data-api
,turso
,d1-http
(WIP), orexpo
. Otherwise, you can remove thedriver
fromdrizzle.config.ts
.connectionString
oruri
indbCredentials
, you should now useurl
.3. If you are using PostgreSQL and had migrations generated in your project, please run
drizzle-kit up
so Drizzle can upgrade all the snapshots to version 6.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.