[Snyk] Upgrade drizzle-orm from 0.30.7 to 0.30.10 #87
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade drizzle-orm from 0.30.7 to 0.30.10.
ℹ️ 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 21 versions ahead of your current version.
The recommended version was released 21 days ago, on 2024-05-01.
Release notes
Package name: drizzle-orm
New Features
🎉
.if()
function added to all WHERE expressionsSelect all users after cursors if a cursor value was provided
Bug Fixes
.all
,.values
,.execute
functions in AWS DataAPIsetWhere
andtargetWhere
fields to.onConflictDoUpdate()
config in SQLite instead of singlewhere
fielddb._.fullSchema
const mySchema = pgSchema('mySchema');
const colors = mySchema.enum('colors', ['red', 'green', 'blue']);
migrate()
function to use batch API (#2137)where
clause in Postgres.onConflictDoUpdate
method intosetWhere
andtargetWhere
clauses, to support bothwhere
cases inon conflict ...
clause (fixes #1628, #1302 via #2056)where
clause in Postgres.onConflictDoNothing
method, as it was placed in a wrong spot (fixes #1628 via #2056)Thanks @ hugo082 and @ livingforjesus!
Bug fixes
@ vercel/postgres
packageneon
drivers - #1542Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs
Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.