Bump Microsoft.EntityFrameworkCore.InMemory and 3 others #243
Conversation
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
Bumps Microsoft.EntityFrameworkCore.InMemory from 9.0.4 to 9.0.11 Bumps Microsoft.NET.Test.Sdk from 17.13.0 to 17.14.1 Bumps Testcontainers.PostgreSql from 4.4.0 to 4.9.0 Bumps xunit.runner.visualstudio from 3.1.0 to 3.1.5 --- updated-dependencies: - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-version: 9.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: default - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 17.14.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: default - dependency-name: Testcontainers.PostgreSql dependency-version: 4.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: default - dependency-name: xunit.runner.visualstudio dependency-version: 3.1.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: default ... Signed-off-by: dependabot[bot] <[email protected]>
Contributor
|
Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details: |
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.
Updated Microsoft.EntityFrameworkCore.InMemory from 9.0.4 to 9.0.11.
Release notes
Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.
9.0.11
Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.10...v9.0.11
9.0.10
Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.9...v9.0.10
9.0.9
Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.8...v9.0.9
9.0.7
Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.6...v9.0.7
9.0.6
Bug Fixes
The translation of
FullTextScorein Cosmos Full-Text Search has been updated to use multiple keywords instead of a keyword array, addressing issues with search accuracy and query compatibility. This resolves #35983 and ensures more reliable full-text search results.#36000 by @maumar
Dependency Updates
Updated the Arcade build infrastructure dependencies for the 8.0 release branch, bringing in the latest improvements and security fixes from the Arcade ecosystem.
#35930 by @dotnet-maestro
Updated Arcade dependencies for the 9.0 release branch, ensuring the build system benefits from the latest tooling and reliability enhancements.
#36006 by @dotnet-maestro
Another update to Arcade dependencies for the 8.0 branch, further aligning with upstream improvements and fixes.
#36085 by @dotnet-maestro
Additional update to Arcade dependencies for the 9.0 branch, maintaining up-to-date build tooling and infrastructure.
#36065 by @dotnet-maestro
Technical Improvements
Integrated various internal commits into the 8.0 release branch, improving code quality, maintainability, and aligning with internal standards.
#35926 by @vseanreesermsft
Additional internal commits merged into the 8.0 branch, further enhancing stability and maintainability.
#36080 by @vseanreesermsft
Integrated internal improvements into the 9.0 branch, ensuring consistency and codebase health.
#36081 by @vseanreesermsft
Infrastructure
Updated the product branding and version numbers to 9.0.6, ensuring that all assemblies and packages reflect the correct release version.
#36044 by @vseanreesermsft
Updated branding for the 8.0 release line to version 8.0.17, keeping versioning consistent across all release artifacts.
#36043 by @vseanreesermsft
Miscellaneous
Automated merge of changes from the 8.0 branch into the 9.0 branch, ensuring that all relevant fixes and improvements are carried forward.
#35927 by @github-actions
Merged the 9.0 branch into the 9.0-staging branch, preparing for further testing and validation before final release.
#36051 by @AndriySvyryd
... (truncated)
9.0.5
Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.4...v9.0.5
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 17.13.0 to 17.14.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
17.14.1
What's Changed
Full Changelog: microsoft/vstest@v17.14.0...v17.14.1
17.14.0
What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
New Contributors
... (truncated)
17.14.0-preview-25107-01
What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
Will probably revert before release:
New Contributors
Full Changelog: microsoft/vstest@v17.13.0...v17.14.0-preview-25107-01
Commits viewable in compare view.
Updated Testcontainers.PostgreSql from 4.4.0 to 4.9.0.
Release notes
Sourced from Testcontainers.PostgreSql's releases.
4.9.0
What's Changed
This release adds a new configuration (
DOCKER_API_VERSION) that lets you pin and downgrade the Docker Engine API version. This was needed because Docker Engine v29 introduced breaking changes that affect Docker.DotNet and Testcontainers for .NET. This release pins the API version to1.44. So far, no issues or negative side effects have been observed.I am also working on updating Docker.DotNet to make it fully compatible with Docker Engine v29. There is already a work-in-progress PR.
Thanks to all the contributors who helped with this release 👍.
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
4.8.1
What's Changed
🐛 Bug Fixes
4.8.0
What's Changed
Thank you to all the contributors 🙌.
In version
4.7.0, we noticed that the reuse hash could change depending on the order of dictionary values. This has been fixed to ensure that dictionary values are processed in a consistent order when generating the reuse hash. As a result, the reuse hash will likely change again with4.8.0.Wait strategies now default to the
Runningmode. This mode expects the container to remain running throughout startup. If the container exits unexpectedly, Testcontainers will throw aContainerNotRunningExceptionthat includes the exit code and container logs.The container startup callback now includes an additional overload that provides the actual container configuration. If you implement
IContainerBuilder<TBuilderEntity, TContainerEntity>, you need to add the container configuration (e.g.,IContainerConfiguration) as a third generic type constraint toIContainerBuilder.IContainerBuilder.WithResourceMappingandIContainer.CopyAsyncnow include two new optional arguments:uidandgid. If you do not need to specify those, use named arguments for the existing parameters:fileModeorct.🚀 Features
WithTarget(string)to image builder (#1534) @HofmeisterAn🐛 Bug Fixes
db.runCommand({hello:1})do detect readiness (#1548) @HofmeisterAn📖 Documentation
IContainerBuilder.WithAutoRemovecode comment (#1546) @hojmark🧹 Housekeeping
... (truncated)
4.7.0
What's Changed
This release doesn't introduce breaking changes to the public API, but it isn't binary compatible due to necessary internal changes. Make sure to update all related packages (Testcontainers modules) to the same version. See more details here. Thanks to all contributors 👏.
🚀 Features
.slnx(solution) file in common directory paths (#1492) @alexander-jesner-AP🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
4.6.0
What's Changed
This is a patch release (but the minor version was already set). It fixes a bug in our Docker.DotNet fork where a wrong HTTP
Connectionheader break Podman and possibly other environments. Shipped a quick fix. Thanks again to @ahaeber and @victor-lambret for the help.🐛 Bug Fixes
🧹 Housekeeping
4.5.0
What's Changed
Big thanks to everyone who contributed to this release 🤜🤛.
🚀 Features
Task<ExecResult>extension methodThrowOnFailure(#1448) @HofmeisterAnDockerUnavailableExceptionwhen Docker is not available (#1308) @0xced🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
3.128.1(#1443) @HofmeisterAnCommits viewable in compare view.
Updated xunit.runner.visualstudio from 3.1.0 to 3.1.5.
Release notes
Sourced from xunit.runner.visualstudio's releases.
No release notes found for this version range.
Commits viewable in compare view.
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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions