fix(deps): update dependency drizzle-kit to ^0.23.1 #888
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]](https://avatars.githubusercontent.com/in/816230?s=60&v=4){kind=small}
![homarr-approvals[bot]](https://avatars.githubusercontent.com/in/911248?s=60&v=4){kind=small}
homarr-renovate
bot
force-pushed
the
renovate/drizzle-kit-0.x
branch
from
200bb90
to
b65dcd3
Compare
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.23.0->^0.23.1Release Notes
drizzle-team/drizzle-kit-mirror (drizzle-kit)
v0.23.1: 0.23.1Compare Source
Fixed an issue with pushing SQLite tables with foreign keys defined using custom names. Previously, such tables were always recreated on each push. In this release, the foreign key name will not affect the detection of differences between the code schema and the database schema. This is because SQLite cannot have foreign key constraint names specified in a DDL create table query, so they should not be used in the diff process
When dropping a column from an SQLite table, there was an issue with accessing the primary key of an undefined column
Fixed issues with sequences, #504, #2643
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.