Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump @prisma/sdk from 2.26.0 to 3.3.0 #284

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Nov 1, 2021

Bumps @prisma/sdk from 2.26.0 to 3.3.0.

Release notes

Sourced from @​prisma/sdk's releases.

3.3.0

Today, we are excited to share the 3.3.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟 

Major improvements & new features

Prisma Data Proxy support in Prisma Client in Early Access, now with support for Cloudflare Workers

In 3.3.0, we're releasing Early Access support for Prisma Client connection pooling using Prisma Data Proxy. The Data Proxy feature of the Prisma Data Platform is now accessible to all users of the Prisma Data Platform (no need to request access).

Solving connection management for serverless environments

Prisma Data Proxy is an intermediary between your app and your database. It manages connection pooling, so you can reliably use traditional databases in Serverless environments.

Users can configure a Data Proxy for free on the Prisma Data Platform and connect their Prisma applications to the proxy by enabling the feature flag for it in their code.

For detailed documentation and instructions please refer to pris.ly/data-proxy.

Running Prisma applications in Cloudflare Workers

Using this new feature in Prisma Client and leveraging the Prisma Data Proxy, developers can now deploy Prisma applications on Cloudflare Workers. Here's what it looks like to use Prisma Client inside of this environment:

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
addEventListener('fetch', (event) => {
event.respondWith(handleRequest(event.request))
})
async function handleRequest(request: Request): Promise<Response> {
await prisma.log.create({
data: {
level: 'Info',
message: ${request.method} ${request.url},
},
})
return new Response(request method: ${request.method}!)
}

Follow this deployment guide to learn how to use Prisma Client with your own Cloudflare Workers. If you run into any problems, you can reach us in this issue!

MongoDB

Support for ordering by relation fields

In 2.16.0, we first introduced ordering by a relation for relational databases. As of today's release, you can now order by a relation field in MongoDB as well:

... (truncated)

Commits
  • 9641fc3 chore(deps): update engines to 3.3.0-30.33838b0f78f1fe9052cf9a00e9761c9dc097a...
  • 340d00b chore(deps): update engines to 3.3.0-29.5b141c65d336b0518ff0e71052c0975860b62...
  • 328857b chore(deps): update engines to 3.3.0-28.2ba62631c379cc1bfcc0d5e0d655e29fadfa6...
  • fc3ed15 chore(migrate): small cleanup, remove double assign (#9831)
  • 058fcbc chore(deps): update engines to 3.3.0-26.9fd694ba5969e515c29e8724d5ddb7b7843f7...
  • bbdf1c2 chore: printWidth from 80 to 120 (#9458)
  • 14cdd28 chore(deps): update engines to 3.3.0-25.fb360459df2a4ca07332a31d6e0fa7e36c173...
  • a4eee08 fix(dbseed): ESM command for db seed for TS help output + fix (#9775)
  • 68fcc27 chore(deps): update engines to 3.3.0-23.1225ee0c71770b84824b529daf2918a6d5a93...
  • 6eda13a Merge pull request #9818 from prisma/renovate/pin-dependencies
  • Additional commits viewable in compare view

Dependabot compatibility score

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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@prisma/sdk](https://github.com/prisma/prisma) from 2.26.0 to 3.3.0.
- [Release notes](https://github.com/prisma/prisma/releases)
- [Commits](prisma/prisma@2.26.0...3.3.0)

---
updated-dependencies:
- dependency-name: "@prisma/sdk"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 1, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github May 1, 2022

Superseded by #317.

@dependabot dependabot bot closed this May 1, 2022
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/prisma/sdk-3.3.0 branch May 1, 2022 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants