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): update dependency dotnet-ef to v5.0.17 #1303

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
dotnet-ef (source) 5.0.4 -> 5.0.17 age adoption passing confidence
dotnet-ef (source) 5.0.8 -> 5.0.17 age adoption passing confidence

Release Notes

dotnet/efcore (dotnet-ef)

v5.0.17: EF Core 5.0.17

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.16.

v5.0.16: EF Core 5.0.16

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.15.

v5.0.15: EF Core 5.0.15

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.14.

v5.0.14: EF Core 5.0.14

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.13.

v5.0.13: EF Core 5.0.13

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.12.

v5.0.12: EF Core 5.0.12

This is a patch release of EF Core 5.0 containing only important bug fixes:

v5.0.11: EF Core 5.0.11

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.10.

v5.0.10: EF Core 5.0.10

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.9.

v5.0.9: EF Core 5.0.9

This is a patch release of EF Core 5.0 containing only important bug fixes.

v5.0.8: EF Core 5.0.8

This is a patch release of EF Core 5.0 containing only important bug fixes.

v5.0.7: EF Core 5.0.7

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.6.

v5.0.6: EF Core 5.0.6

This is a patch release of EF Core 5.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 5.0.5.

v5.0.5: EF Core 5.0.5

This is a patch release of EF Core 5.0 containing only important bug fixes.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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, check this box

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

Copy link

sonarqubecloud bot commented Mar 2, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@rnwood rnwood merged commit 45d801c into master Mar 2, 2024
17 checks passed
@rnwood rnwood deleted the renovate/dotnet-monorepo branch March 2, 2024 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant