build: Bump the testing group with 6 updates#171
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
build: Bump the testing group with 6 updates#171dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps AwesomeAssertions from 9.3.0 to 9.4.0 Bumps coverlet.collector from 6.0.4 to 8.0.1 Bumps Moq.Analyzers from 0.4.0 to 0.4.2 Bumps Reqnroll from 3.3.1 to 3.3.3 Bumps Reqnroll.xUnit from 3.3.1 to 3.3.3 Bumps xunit.analyzers from 1.26.0 to 1.27.0 --- updated-dependencies: - dependency-name: AwesomeAssertions dependency-version: 9.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: testing - dependency-name: coverlet.collector dependency-version: 8.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: testing - dependency-name: Moq.Analyzers dependency-version: 0.4.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: testing - dependency-name: Reqnroll dependency-version: 3.3.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: testing - dependency-name: Reqnroll.xUnit dependency-version: 3.3.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: testing - dependency-name: xunit.analyzers dependency-version: 1.27.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
This Dependabot PR contains a version-update:semver-major update and requires manual review before merging. |
|
Contributor
Author
|
Looks like these dependencies are updatable in another way, 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.
Updated AwesomeAssertions from 9.3.0 to 9.4.0.
Release notes
Sourced from AwesomeAssertions's releases.
9.4.0
What's Changed
New features
Improvements
Fixes
Documentation
Dependencies
... (truncated)
Commits viewable in compare view.
Updated coverlet.collector from 6.0.4 to 8.0.1.
Release notes
Sourced from coverlet.collector's releases.
8.0.1
Fixed
Improvements
Diff between 8.0.0 and 8.0.1
8.0.0
Special Thanks: A huge thank you to @Bertk for driving the majority of the work in this release! 🎉
Fixed
Improvements
Diff between 6.0.4 and 8.0.0
Commits viewable in compare view.
Updated Moq.Analyzers from 0.4.0 to 0.4.2.
Release notes
Sourced from Moq.Analyzers's releases.
0.4.2
Moq.Analyzers 0.4.2 🎉
This is a focused patch release with one mission: squash a false positive that was getting in the way of real-world LINQ-to-Mocks usage. If you've been seeing Moq1302 warnings on perfectly valid code, this one's for you. 🎯
A big thank you to @abatishchev for reporting the issue with a clear, actionable reproduction. Community reports like this make all the difference.
🐛 False Positive Fix for Moq1302
What was happening
If you were using
Mock.Ofwith a comparison expression — something totally normal like this:…you'd get a warning:
But there's nothing wrong with that code. It compiles, it runs, and it's how LINQ-to-Mocks expressions are supposed to work. The right-hand side of the comparison (
StatusCodes.Status200OK) is just a constant — it's not a mock setup member. The analyzer shouldn't have been looking at it at all. 😬The same false positive appeared with enum values, static fields, external locals, and other non-mock expressions on the right-hand side of
==,&&, or||comparisons.How it was fixed
The fix introduces a lambda parameter guard: before the analyzer flags a member access, it now walks the receiver chain to check whether the operation is actually rooted in the lambda parameter (i.e., the
rinr => r.Status == ...).A new
IsRootedInLambdaParameter()extension method traces the receiver chain — through property accesses, method calls, and conversions — all the way back to the lambda parameter. If the chain doesn't terminate in the lambda parameter, the member is silently skipped. Static members, constants, and external references pass right through without a warning.The guard is applied only to leaf member operations (property references, method calls). Composite operations like
&&and||still get decomposed normally, so chained comparisons liker.Prop == "a" && r.Other == "b"continue to be fully analyzed. No false negatives.As a bonus,
MoqKnownSymbolsis now threaded through the entire analysis chain instead of being recreated mid-analysis, and nestedMock.Ofcalls are excluded early to prevent false positives from inner mock expressions.🧪 Comprehensive Test Coverage
This release adds 961 new lines of test code covering the full surface area of the fix (#1020):
&&/||expressionsMock.Ofcalls👥 Contributors
Thank you to everyone who reported bugs and provided reproduction cases:
... (truncated)
0.4.1
Moq.Analyzers 0.4.1
This is a patch release addressing critical bugs reported after v0.4.0.
🐛 Bug Fixes
Moq1203 False Positives
ReturnsAsync,Callback, and similar chained methods. (#886, #919)Setupcall is wrapped in parentheses. (#895)Parenthesized Expression Handling
Assembly Loading
CS8032warning caused bySystem.Collections.Immutableassembly version mismatch. (#888)🤝 Contributors
Thank you to everyone who reported bugs, provided reproduction cases, and engaged in issue discussions to help make this release possible:
🔗 Resources
💬 Feedback
If you encounter any issues or have suggestions:
Thank you for using Moq.Analyzers!
0.4.1-alpha
v0.4.1-alpha
Prerelease containing 3 bug fixes since v0.4.0 to rebuild confidence with users.
Bug Fixes
Critical: CS8032 Fix
v0.4.0 shipped DLLs that referenced
System.Collections.Immutableversions incompatible with .NET 8 SDK hosts, causing CS8032 warnings on every build. This release downgrades the transitive dependency pins and adds CI load tests to prevent recurrence.Commits viewable in compare view.
Updated Reqnroll from 3.3.1 to 3.3.3.
Release notes
Sourced from Reqnroll's releases.
3.3.3
Improvements:
Bug fixes:
Contributors of this release (in alphabetical order): @clrudolphi
3.3.2
Bug fixes:
Contributors of this release (in alphabetical order): @clrudolphi, @gasparnagy
Commits viewable in compare view.
Updated Reqnroll.xUnit from 3.3.1 to 3.3.3.
Release notes
Sourced from Reqnroll.xUnit's releases.
3.3.3
Improvements:
Bug fixes:
Contributors of this release (in alphabetical order): @clrudolphi
3.3.2
Bug fixes:
Contributors of this release (in alphabetical order): @clrudolphi, @gasparnagy
Commits viewable in compare view.
Updated xunit.analyzers from 1.26.0 to 1.27.0.
Release notes
Sourced from xunit.analyzers'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 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