-
Notifications
You must be signed in to change notification settings - Fork 731
Bump Verify.Xunit from 28.1.3 to 28.2.0 in the xunit group #2813
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
Conversation
Bumps the xunit group with 1 update: [Verify.Xunit](https://github.com/VerifyTests/Verify). Updates `Verify.Xunit` from 28.1.3 to 28.2.0 - [Release notes](https://github.com/VerifyTests/Verify/releases) - [Commits](VerifyTests/Verify@28.1.3...28.2.0) --- updated-dependencies: - dependency-name: Verify.Xunit dependency-type: direct:production update-type: version-update:semver-minor dependency-group: xunit ... Signed-off-by: dependabot[bot] <support@github.com>
Qodana for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at qodana-support@jetbrains.com
|
Test Results 32 files ±0 32 suites ±0 2m 45s ⏱️ +14s Results for commit 7002c3f. ± Comparison against base commit ef7c334. This pull request removes 10 and adds 8 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Pull Request Test Coverage Report for Build 11781311984Details
💛 - Coveralls |
Bumps the xunit group with 1 update: Verify.Xunit.
Updates
Verify.Xunitfrom 28.1.3 to 28.2.0Commits
c889294Update Directory.Build.propsb69b639Apply scrubbing to dictionary keys (#1342)d89cddfmove to HandleDictionaryIteme0defd9avoid load type in ResolveDictionaryKey2e83808split CustomContractResolver231191erefsb630988Update Directory.Packages.propsb831f2arefs3383c59refs or cleanupe6596adMerge branch 'main' of https://github.com/VerifyTests/VerifyDependabot 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