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

chore(deps): bump @prisma/client from 4.14.1 to 4.15.0 #132

Closed
wants to merge 2 commits into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 10, 2023

Bumps @prisma/client from 4.14.1 to 4.15.0.

Release notes

Sourced from @​prisma/client's releases.

4.15.0

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

Highlights

For this release, we focused on fixing bugs and making smaller quality-of-life improvements.

Support for custom arguments for prisma db seed

This release adds support for defining and passing arbitrary arguments to prisma db seed. This creates the opportunity for you to define your own arguments in your seed file that you could pass to the prisma db seed command. A few example use-cases include, but are not limited to:

  • Seeding different data in different environments
  • Partially seeding data in some tables

Here is an example seed.ts file that defines custom arguments for seeding different data in different environments:

// prisma/seed.ts
import { parseArgs } from "node:util";
const options = {
environment: { type: 'string', },
}
async function main() {
const { values: { environment } } = parseArgs({ options })
switch (environment) {
case "development":
/** do something for development /
break;
case "test":
/* do something  for test  environment */
break;
default:
break;
}
}
main()

You can then provide the environment argument when executing the seed script as follows:

npx prisma db seed -- --environment development

Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.

... (truncated)

Commits
  • 1ec901e chore(deps): update engines to 4.16.0-1.20e9482aa10ecccd153228a85b1327a79bff4...
  • 550812e chore(deps): update dependency expect-type to v0.16.0 (#19507)
  • ab8d4e3 revert: "chore(deps): update engines to 4.15.0-29.88c73fb4b0dbbf8a7e6a7809c31...
  • f755d71 chore(client): remove bundler warning (#19479)
  • b5dadf6 chore(deps): update engines to 4.15.0-29.88c73fb4b0dbbf8a7e6a7809c31006efeb08...
  • b516503 fix(vsce): send reload signal to vscode extension (#19457)
  • 9396916 chore(deps): update engines to 4.15.0-28.8fbc245156db7124f997f4cecdd8d1219e36...
  • 79852ee chore: remove outdated comment (#19472)
  • 3f8e807 fix: client fails to reconnect after failure (#19422)
  • 99d9a52 chore(deps): update engines to 4.15.0-27.4cb6fe5bf17152944b142d7db2cd65843ec3...
  • 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)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 10, 2023
@trpc-bot trpc-bot force-pushed the main branch 4 times, most recently from d7439ce to e107510 Compare June 11, 2023 16:33
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/prisma/client-4.15.0 branch from 169a67e to 307d858 Compare June 11, 2023 16:36
@trpc-bot trpc-bot force-pushed the main branch 4 times, most recently from 1b00327 to 9488627 Compare June 15, 2023 18:12
Bumps [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) from 4.14.1 to 4.15.0.
- [Release notes](https://github.com/prisma/prisma/releases)
- [Commits](https://github.com/prisma/prisma/commits/4.15.0/packages/client)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/prisma/client-4.15.0 branch from 307d858 to ad1f627 Compare June 18, 2023 11:03
@trpc-bot trpc-bot force-pushed the main branch 3 times, most recently from 27ee0f0 to 722dc5e Compare June 19, 2023 13:08
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 21, 2023

Superseded by #133.

@dependabot dependabot bot closed this Jun 21, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/prisma/client-4.15.0 branch June 21, 2023 00:06
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