Update dependency knex to v1 #15
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/knex-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.95.0
->1.0.1
Release Notes
knex/knex
v1.0.1
Compare Source
Bug fixes:
v1.0.0
Compare Source
Breaking changes
sqlite3
driver with@vscode/sqlite3
;RETURNING
operation to be consistent withSELECT
;New features:
Bug fixes:
Typings:
v0.95.15
Compare Source
Bug fixes:
v0.95.14
Compare Source
Bug fixes:
v0.95.13
Compare Source
Bug fixes:
Typings:
v0.95.12
Compare Source
New features:
Bug fixes:
Typings:
v0.95.11
Compare Source
New features:
Bug fixes:
Improvements:
v0.95.10
Compare Source
Improvements:
Typings:
v0.95.9
Compare Source
New features:
Typings:
v0.95.8
Compare Source
New features:
Bug fixes:
Typings:
v0.95.7
Compare Source
New features:
Typings:
v0.95.6
Compare Source
Typings:
v0.95.5
Compare Source
New features:
Bug fixes:
Typings:
v0.95.4
Compare Source
Typings:
v0.95.3
Compare Source
New features:
Bug fixes:
Typings:
v0.95.2
Compare Source
New features:
Bug fixes:
Typings:
Test / internal changes:
v0.95.1
Compare Source
Bug fixes:
Configuration
📅 Schedule: 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.
9774d40935
to1ed80e8419
This breaks stuff (the hard way)
Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 1.x releases. However, if you upgrade to 1.x manually then Renovate will then reenable updates for minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.
Pull request closed