Closed
Conversation
Bumps Azure.Identity from 1.12.0 to 1.16.0 Bumps Azure.Storage.Blobs from 12.22.2 to 12.25.0 Bumps Testcontainers from 3.8.0 to 4.7.0 Bumps Xunit.SkippableFact from 1.4.13 to 1.5.23 --- updated-dependencies: - dependency-name: Azure.Identity dependency-version: 1.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-deps - dependency-name: Azure.Identity dependency-version: 1.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-deps - dependency-name: Azure.Storage.Blobs dependency-version: 12.25.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-deps - dependency-name: Azure.Storage.Blobs dependency-version: 12.25.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-deps - dependency-name: Testcontainers dependency-version: 4.7.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-deps - dependency-name: Xunit.SkippableFact dependency-version: 1.5.23 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
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.
Pinned Azure.Identity at 1.16.0.
Release notes
Sourced from Azure.Identity's releases.
1.16.0
1.16.0 (2025-09-09)
Features Added
DefaultAzureCredentialconstructor that accepts a custom environment variable name for credential configuration. This provides flexibility beyond the defaultAZURE_TOKEN_CREDENTIALSenvironment variable. The constructor accepts any environment variable name and uses the same credential selection logic as the existingAZURE_TOKEN_CREDENTIALSprocessing.DefaultAzureCredential.DefaultEnvironmentVariableNameconstant property that returns"AZURE_TOKEN_CREDENTIALS"for convenience when referencing the default environment variable name.AzureCliCredential,AzurePowerShellCredential, andAzureDeveloperCliCredentialnow throw anAuthenticationFailedExceptionwhen theTokenRequestContextincludes claims, as these credentials do not support claims challenges. The exception message includes guidance for handling such scenarios.AZURE_TOKEN_CREDENTIALSor the equivalent custom environment variable is configured toManagedIdentityCredential, theDefaultAzureCredentialdoes not issue a probe request and performs retries with exponential backoff.Bugs Fixed
AzureDeveloperCliCredentialhanging when theAZD_DEBUGenvironment variable is set by adding the--no-promptflag to prevent interactive prompts (#52005).BrokerCredentialis now included in the chain whenAZURE_TOKEN_CREDENTIALSis set todev.DefaultAzureCredentialthat caused the credential chain to be constructed incorrectly when using AZURE_TOKEN_CREDENTIALS in combination withDefaultAzureCredentialOptions.Other Changes
BrokerCredentialis now always included in theDefaultAzureCredentialchain. If theAzure.Identity.Brokerpackage is not referenced, an exception will be thrown whenGetTokenis called, making its behavior consistent with the rest of the credentials in the chain.Microsoft.Identity.Clientdependency to version 4.76.0.Microsoft.Identity.Client.Extensions.Msaldependency to version 4.76.0.1.15.0
1.15.0 (2025-08-07)
Breaking Changes
Behavioral Breaking Changes
SharedTokenCacheCredential. The supporting credential (SharedTokenCacheCredential) was a legacy mechanism for authenticating clients using credentials provided to Visual Studio. For brokered authentication, consider usingInteractiveBrowserCredentialinstead. The following changes have been made:SharedTokenCacheCredentialclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialOptionsclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]DefaultAzureCredentialOptions.ExcludeSharedTokenCacheCredentialproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheUsernameproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialis no longer included in theDefaultAzureCredentialauthentication flowBugs Fixed
AdditionallyAllowedTenantsvalues which will now be matched against tenant IDs without case sensitivity, making the authentication more resilient to case differences in tenant IDs returned from WWW-Authenticate challenges (#51693).Other Changes
BrokerAuthenticationCredentialhas been renamed asBrokerCredential.Added the
EditorBrowsable(Never)attribute to propertyVisualStudioCodeTenantIdasTenantIdis preferred. TheVisualStudioCodeTenantIdproperty exists only to provide backwards compatibility.Commits viewable in compare view.
Pinned Azure.Storage.Blobs at 12.25.0.
Release notes
Sourced from Azure.Storage.Blobs's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Testcontainers from 3.8.0 to 4.7.0.
Release notes
Sourced from Testcontainers's releases.
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) @HofmeisterAn4.4.0
What's Changed
Time for a new release! Big thanks to everyone who helped out with this one. It's got some awesome new features and fixes 😎. Seriously, I can't thank you enough. This wouldn't be possible without your ongoing support 🙏.
🚀 Features
🐛 Bug Fixes
WithName(IImage)(#1413) @HofmeisterAnCreatedTimeforUntilMessageIsLoggedwait strategy (#1384) @0xced📖 Documentation
testcontainers/helloworldimage in docs to version1.2.0(#1419) @VishnuJin🧹 Housekeeping
4.3.0
What's Changed
Thank you to all the contributors 🙌.
🚀 Features
🐛 Bug Fixes
🧹 Housekeeping
SharedContainerInstanceand useContainerFixtureinstead (#1378) @0xced4.2.0
What's Changed
Thanks for all the contributions. Great first release of the year ❤️.
🚀 Features
🐛 Bug Fixes
🧹 Housekeeping
4.1.0
What's Changed
This is likely the last release for this year, unless urgent fixes become necessary.
I want to mention a change introduced in the last major release, where we refactored the
IImageinterface. As part of this update, we removed obsolete properties and overloaded constructors. If you previously used an overload other thanDockerImage(string), please ensure you pass the correct values to the constructor.Additionally, we replaced Docker.DotNet with our own fork to keep the Docker Engine API up to date. Our goal is to improve reliability and performance while offering a more developer-friendly and convenient client. If you depend on a Docker client for .NET, we encourage you to contribute to this project ❤️.
On a personal note, I wish everyone a peaceful and lovely holiday season. Take this time to rest, connect with loved ones, and recharge for the new year. Take care.
🚀 Features
net6.0and addnet9.0TFM (#1311) @HofmeisterAn🐛 Bug Fixes
DbContainerFixtureto match the behavior ofContainerFixture(#1310) @0xced📖 Documentation
🧹 Housekeeping
4.0.0
What's Changed
Thanks so much for all the effort you put into this release 🙌. We are continuing to align Testcontainers for .NET with other language implementations and working on improving the domain-specific language.
We have updated the
IImageinterface to follow the domain-specific language with the correct property names. The table below shows the changes. We tried to make the transition as smooth as possible, but be aware that relying on theRepositoryproperty might cause issues since it now resolves a different value than before. We have kept the old properties, marked them as obsolete, and provided guidance on how to migrate.and Papercutmodule (#1265) @HofmeisterAnIImageproperties with Docker DSL (#1256) @HofmeisterAn🚀 Features
execto replace current shell with the Kafka process (as ENTRYPOINT) (#1282) @jasoncoutureWithEnterpriseEdition(bool)) (#1269) @SossenbinderIImage,DockerImageand in theWithImage(string)implementation (#1249) @KielekIImageproperties with Docker DSL (#1256) @HofmeisterAnAccountNameandAccountKeyto public, move toAzuriteBuilder(#1258) @mikecole🐛 Bug Fixes
🧹 Housekeeping
3.10.0
Hey everyone, just wanted to say a huge thanks to all of you who helped with this version — whether through contributions, reporting issues, or discussions. I've been very busy lately, and your support has been a huge help. I really appreciate it!
What's Changed
🚀 Features
MatchVersion(Predicate<Version>)(#1231) @0xced🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
latestPatchtolatestMinor(#1230) @0xced3.9.0
Thank you to everyone whose contributions made this release possible.
What's Changed
The
UntilOperationIsSucceeded(Func<bool>, int, Action<IWaitStrategy>)wait strategy is obsolete. Instead of this wait strategy, use any other wait strategy that matches your use case and configure the retry behavior accordingly (wait strategy options).Using reuse together with the container builder method
WithName(string)will generate a new reuse hash the first time you use the configuration. The container name was not included in calculating the reuse hash previously.🚀 Features
🐛 Bug Fixes
/var/lib/mysql-filesdirectory to prevent older versions from failing to start (#1144) @0xced📖 Documentation
🧹 Housekeeping
📦 Dependency Updates
Commits viewable in compare view.
Updated Xunit.SkippableFact from 1.4.13 to 1.5.23.
Release notes
Sourced from Xunit.SkippableFact's releases.
1.5.23
What's Changed
#ifregions by @AArnott in Remove dead#ifregions AArnott/Xunit.SkippableFact#39New Contributors
Full Changelog: AArnott/Xunit.SkippableFact@v1.4.13...v1.5.22
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