[Snyk] Upgrade drizzle-kit from 0.21.4 to 0.24.2 #2
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.
Snyk has created this PR to upgrade drizzle-kit from 0.21.4 to 0.24.2.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 137 versions ahead of your current version.
The recommended version was released on 2 months ago.
Issues fixed by the recommended upgrade:
SNYK-JS-INFLIGHT-6095116
Release notes
Package name: drizzle-kit
New Features
🎉 Support for
pglite
driverYou can now use pglite with all drizzle-kit commands, including Drizzle Studio!
export default defineConfig({
dialect: "postgresql",
driver: "pglite",
schema: "./schema.ts",
dbCredentials: {
url: "local-pg.db",
},
verbose: true,
strict: true,
});
Bug fixes
Bug fixes
What was fixed
introspect
command.::<type>
was included in the introspected output.preserve
casing option was brokenTickets that were closed
Breaking changes (for SQLite users)
Fixed Composite primary key order is not consistent by removing
sort
in SQLite and to be consistent with the same logic in PostgreSQL and MySQLThe issue that may arise for SQLite users with any driver using composite primary keys is that the order in the database may differ from the Drizzle schema.
If you are using
push
, you MAY be prompted to update your table with a new order of columns in the composite primary key. You will need to either change it manually in the database or push the changes, but this may lead to data loss, etc.If you are using
generate
, you MAY also be prompted to update your table with a new order of columns in the composite primary key. You can either keep that migration or skip it by emptying the SQL migration file.If nothing works for you and you are blocked, please reach out to me @ AndriiSherman. I will try to help you!
Bug fixes
schemaFilter
object was passed. It was detecting enums even in schemas that were not defined in the schemaFilter.drizzle-kit up
command to work as expected, starting from the sequences release.Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
Description by Korbit AI
What change is being made?
Upgrade the
drizzle-kit
package from version 0.21.1 to 0.24.2 in thepackage.json
file.Why are these changes being made?
This upgrade addresses potential security vulnerabilities and includes performance improvements and new features introduced in the latest version of
drizzle-kit
. Keeping dependencies up-to-date ensures the application remains secure and benefits from the latest enhancements.