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

Update prisma monorepo to v3.9.1 #4345

Merged
merged 1 commit into from
Feb 2, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 3.9.0 -> 3.9.1 age adoption passing confidence
@prisma/sdk (source) 3.9.0 -> 3.9.1 age adoption passing confidence
prisma (source) 3.9.0 -> 3.9.1 age adoption passing confidence

Release Notes

prisma/prisma

v3.9.1

Compare Source

Today, we are issuing the 3.9.1 patch release.

Fixes


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot added the release:chore This PR is a chore (means nothing for users) label Feb 2, 2022
@renovate renovate bot assigned jtoar Feb 2, 2022
@thedavidprice thedavidprice merged commit 18720cd into main Feb 2, 2022
@thedavidprice thedavidprice deleted the renovate/prisma-monorepo branch February 2, 2022 21:11
@jtoar jtoar added this to the next-release milestone Feb 2, 2022
@thedavidprice thedavidprice modified the milestones: next-release, v0.44.0 Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:chore This PR is a chore (means nothing for users)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants