build(deps-dev): bump prisma from 6.19.1 to 7.2.0 in /typescript/prisma#284
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
build(deps-dev): bump prisma from 6.19.1 to 7.2.0 in /typescript/prisma#284dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/typescript/prisma/prisma-7.2.0
branch
5 times, most recently
from
c490cb6 to
efb6a1c
Compare
Bumps [prisma](https://github.com/prisma/prisma/tree/HEAD/packages/cli) from 6.19.1 to 7.2.0. - [Release notes](https://github.com/prisma/prisma/releases) - [Commits](https://github.com/prisma/prisma/commits/7.2.0/packages/cli) --- updated-dependencies: - dependency-name: prisma dependency-version: 7.2.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/typescript/prisma/prisma-7.2.0
branch
from
efb6a1c to
0cf5f22
Compare
Contributor
Author
|
Superseded by #375. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/typescript/prisma/prisma-7.2.0
branch
amaksimo
pushed a commit
that referenced
this pull request
Jan 29, 2026
This PR updates the Prisma sample from Prisma v6 to Prisma v7. There were major version changes which caused incompatibilities with our previous sample, such that Dependabot was unable to complete the upgrade without manual changes. It tried in #295 and #284. The major change is the replacement of `DATABASE_URL` with a `prisma.config.ts` file. This is quite convenient for DSQL since previously it was awkward for users to generate a token and embed it in the `DATABASE_URL` variable, given the password would expire. Now we can generate a token on the fly as part of the `prisma.config.ts` file like we do in our connector libraries. You will notice that it's now necessary to provide `CLUSTER_ENDPOINT` even when doing things like `npm run build` which doesn't make a lot of sense, but this seems to be a side-effect of the way Prisma requires the configuration file any time a Prisma command is run. We could probably provide a dummy URL or something but that may be confusing in the sample code, and in practice it's easy to define the `CLUSTER_ENDPOINT` env var first and just leave it defined. In practice I think users may hard code their endpoint in the config file anyway, in which case this won't be an issue. By submitting this pull request, I confirm that my contribution is made under the terms of the MIT-0 license.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps prisma from 6.19.1 to 7.2.0.
Release notes
Sourced from prisma's releases.
... (truncated)
Commits
815ba13chore(cli): bump@prisma/dev, fix init usage following changes. (#28929)bebccbdfeat(cli): customizeprisma initbased on the JS runtime (Bun vs other) (#2...09b4a1dfix(cli): makeprisma version --jsonemit JSON only to stdout (#28911)ed03287feat(config): allow undefined urls in e.g.prisma generate(#28895)f80a3d3chore(cli): bump@prisma/dev. (#28924)fdbf663chore(cli): bump@prisma/studio-coreto latest with proper licensing. (#28923)f85de48refactor(cli): bump@prisma/devand usestartPrismaDevServerinstead of t...9c14872fix(cli): studio mishandles remote "prisma+postgres:" connection strings. (#2...f27b66brefactor: TML-1654 use management api sdk init command (#28878)0506a3afix: remove pool param for studio ppg connections (#28883)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)