Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.
Fixes in Prisma CLI
Windows-only fix for new D1 specific flags for migrate diff and db pull
The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.
We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:
[✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using PowerShell) #23702](prisma/prisma#23702)
Today, we are excited to share the 5.12.0 stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release.
Highlights
Cloudflare D1 (Preview)
This release brings Preview support for Cloudflare D1 with Prisma ORM 🥳
D1 is Cloudflare’s SQLite database that can be used when deploying applications with Cloudflare.
When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite as your database provider in your Prisma schema, and interact with your database using Prisma Client.
To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite as your database provider and use the @prisma/adapter-d1 database adapter via the driverAdapters Preview feature, released back in version 5.4.0.
Here is an example of sending a query to your D1 database using Prisma Client in your Worker:
// src/index.ts file
import { PrismaClient } from '@prisma/client'
import { PrismaD1 } from '@prisma/adapter-d1'
// Add the D1Database to the Env interface
export interface Env {
</tr></table>
... (truncated)
Commits
af7b771 chore(deps): update engines to 5.12.0-21.473ed3124229e22d881cb7addf559799deba...
671a742 chore(deps): update dependency @libsql/client to v0.6.0 (#23658)
e7b60d1 chore(deps): update dependency @cloudflare/workers-types to v4.20240329.0 (#2...
7d1162b chore(deps): update engines to 5.12.0-19.473ed3124229e22d881cb7addf559799deba...
09f640d fix(adapter-d1): Correctly treat CURRENT_TIMESTAMP result as date (#23649)
dfac408 chore(deps): update engines to 5.12.0-17.12fad4795eef0c21ed444646215f274961d9...
Add a new top-level deprecations object, which contains various
Deprecation objects that define the different types of deprecation used by
the Sass compiler and can be passed to the options below.
Add a new fatalDeprecations compiler option that causes the compiler to
error if any deprecation warnings of the provided types are encountered. You
can also pass in a Version object to treat all deprecations that were active
in that Dart Sass version as fatal.
Add a new futureDeprecations compiler option that allows you to opt-in to
certain deprecations early (currently just import).
Add a new silenceDeprecations compiler option to ignore any deprecation
warnings of the provided types.
Command-Line Interface
Add a new --silence-deprecation flag, which causes the compiler to ignore
any deprecation warnings of the provided types.
Previously, if a future deprecation was passed to --fatal-deprecation but
not --future-deprecation, it would be treated as fatal despite not being
enabled. Both flags are now required to treat a future deprecation as fatal
with a warning emitted if --fatal-deprecation is passed without
--future-deprecation, matching the JS API's behavior.
Dart API
The compile methods now take in a silenceDeprecations parameter, which
causes the compiler to ignore any deprecation warnings of the provided types.
Add Deprecation.obsoleteIn to match the JS API. This is currently null for
all deprecations, but will be used once some deprecations become obsolete in
Dart Sass 2.0.0.
Potentially breaking bug fix: Fix a bug where compileStringToResultAsync
ignored fatalDeprecations and futureDeprecations.
The behavior around making future deprecations fatal mentioned in the CLI
section above has also been changed in the Dart API.
Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.
Fixes in Prisma CLI
Windows-only fix for new D1 specific flags for migrate diff and db pull
The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.
We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:
[✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using PowerShell) #23702](prisma/prisma#23702)
Today, we are excited to share the 5.12.0 stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release.
Highlights
Cloudflare D1 (Preview)
This release brings Preview support for Cloudflare D1 with Prisma ORM 🥳
D1 is Cloudflare’s SQLite database that can be used when deploying applications with Cloudflare.
When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite as your database provider in your Prisma schema, and interact with your database using Prisma Client.
To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite as your database provider and use the @prisma/adapter-d1 database adapter via the driverAdapters Preview feature, released back in version 5.4.0.
Here is an example of sending a query to your D1 database using Prisma Client in your Worker:
// src/index.ts file
import { PrismaClient } from '@prisma/client'
import { PrismaD1 } from '@prisma/adapter-d1'
// Add the D1Database to the Env interface
export interface Env {
</tr></table>
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the minor group with 12 updates:
6.5.1
6.5.2
6.5.1
6.5.2
6.5.1
6.5.2
5.11.0
5.12.1
1.72.0
1.74.1
20.12.2
20.12.5
18.2.73
18.2.74
18.2.23
18.2.24
7.4.0
7.6.0
7.4.0
7.6.0
5.11.0
5.12.1
5.4.3
5.4.4
Updates
@fortawesome/fontawesome-svg-core
from 6.5.1 to 6.5.2Release notes
Sourced from
@fortawesome/fontawesome-svg-core
's releases.Commits
c0f460d
Release 6.5.2 (#20179)a1232e3
Delete case-sensitive faTshirt duplicate (#20073)dcdc48a
Update contributing guidelines (#20028)Updates
@fortawesome/free-brands-svg-icons
from 6.5.1 to 6.5.2Release notes
Sourced from
@fortawesome/free-brands-svg-icons
's releases.Commits
c0f460d
Release 6.5.2 (#20179)a1232e3
Delete case-sensitive faTshirt duplicate (#20073)dcdc48a
Update contributing guidelines (#20028)Updates
@fortawesome/free-solid-svg-icons
from 6.5.1 to 6.5.2Release notes
Sourced from
@fortawesome/free-solid-svg-icons
's releases.Commits
c0f460d
Release 6.5.2 (#20179)a1232e3
Delete case-sensitive faTshirt duplicate (#20073)dcdc48a
Update contributing guidelines (#20028)Updates
@prisma/client
from 5.11.0 to 5.12.1Release notes
Sourced from
@prisma/client
's releases.... (truncated)
Commits
af7b771
chore(deps): update engines to 5.12.0-21.473ed3124229e22d881cb7addf559799deba...671a742
chore(deps): update dependency@libsql/client
to v0.6.0 (#23658)e7b60d1
chore(deps): update dependency@cloudflare/workers-types
to v4.20240329.0 (#2...7d1162b
chore(deps): update engines to 5.12.0-19.473ed3124229e22d881cb7addf559799deba...09f640d
fix(adapter-d1): Correctly treat CURRENT_TIMESTAMP result as date (#23649)dfac408
chore(deps): update engines to 5.12.0-17.12fad4795eef0c21ed444646215f274961d9...b6efac2
chore(deps): update definitelytyped (#23550)d8ee9b2
chore(deps): update dependency@types/node
to v16.18.91 (#23464)85f43be
chore(deps): update engines to 5.12.0-14.ac6cd787ad122596242218dca95c086051e2...0566ebb
chore(deps): update engines to 5.12.0-13.582bc82c6e2ef356990286ce3082af371dd7...Updates
sass
from 1.72.0 to 1.74.1Release notes
Sourced from sass's releases.
Changelog
Sourced from sass's changelog.
... (truncated)
Commits
1137797
Fix bulma and release 1.74.1 (#2210)d9220d9
Complete implementation the deprecations API (#2207)783c248
Fix typo in function documentation (#2205)c8d0643
Better handle filesystem importers when load paths aren't necessary (#2203)9302b35
Add support for nesting in plain CSS (#2198)772280a
Support linux-riscv64 and windows-arm64 (#2201)Updates
@types/node
from 20.12.2 to 20.12.5Commits
Updates
@types/react
from 18.2.73 to 18.2.74Commits
Updates
@types/react-dom
from 18.2.23 to 18.2.24Commits
Updates
@typescript-eslint/eslint-plugin
from 7.4.0 to 7.6.0Release notes
Sourced from
@typescript-eslint/eslint-plugin
's releases.Changelog
Sourced from
@typescript-eslint/eslint-plugin
's changelog.Commits
e1db872
chore(release): publish 7.6.0a6ab2cb
feat: bump npm dependency ranges (#8860)4bac40c
docs: fix incorrect tab item values in prefer-optional-chain (#8867)a7bdd1c
test(eslint-plugin): render snapshots of ESLint output for each code example ...41d893f
docs(eslint-plugin): [consistent-return] add warning section use noImplicitRe...d063275
docs: feature-freeze member-ordering, naming-convention, sort-type-constituen...a14ba9d
chore(release): publish 7.5.0ecb6b55
docs: add homepage (#8742)f0b1c4f
fix(eslint-plugin): [no-unnecessary-type-assertion] handle exactOptionalPrope...5707268
fix(eslint-plugin): [no-floating-promises] handle TaggedTemplateExpression (#...Updates
@typescript-eslint/parser
from 7.4.0 to 7.6.0Release notes
Sourced from
@typescript-eslint/parser
's releases.Changelog
Sourced from
@typescript-eslint/parser
's changelog.Commits
e1db872
chore(release): publish 7.6.0a6ab2cb
feat: bump npm dependency ranges (#8860)a14ba9d
chore(release): publish 7.5.0ecb6b55
docs: add homepage (#8742)d5615d7
fix(parser): disallowerrorOnTypeScriptSyntacticAndSemanticIssues
(#8784)Updates
prisma
from 5.11.0 to 5.12.1Release notes
Sourced from prisma's releases.
... (truncated)
Commits
2c09e72
feat(migrate diff): add -o --output option (#23715)dcdeac0
chore: iterate promo messages (#23657)b6efac2
chore(deps): update definitelytyped (#23550)2129a5b
chore(deps): update definitelytyped (#23463)7b0dd40
chore(deps): update devdependencies patch (non-major) (#23465)Updates
typescript
from 5.4.3 to 5.4.4Release notes
Sourced from typescript's releases.
Commits
8eb3367
Bump version to 5.4.4 and LKGde9096b
🤖 Pick PR #57871 (Divide-and-conquer strategy for int...) into release-5.4 (#...06aae98
🤖 Pick PR #57973 (Compare package.json paths with cor...) into release-5.4 (#...6d8134e
🤖 Pick PR #57637 (Fixed a regression related to deter...) into release-5.4 (#...1c25c7f
🤖 Pick PR #57968 (Normalize slashes for paths in watc...) into release-5.4 (#...3caec2c
Cherry pick PR 57887 into release-5.4 (#57898)896947e
🤖 Pick PR #57938 (Directories dont check modified tim...) into release-5.4 (#...521d3fb
🤖 Pick PR #57950 (Watch events enhancements) into release-5.4 (#57967)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show