Repository navigation
chore(deps): update dependency imposter to 1.0.6 - #7258
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update the managed package version Directory.Packages.props |
The centrally managed Imposter package version changes from 1.0.5 to 1.0.6. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Possibly related PRs
- thomhurst/TUnit#7247: This PR advances the same centrally managed
Imposterpackage version from 1.0.5 to 1.0.6. - thomhurst/TUnit#7244: This PR updates the same package from 1.0.3 to 1.0.4, earlier in the version sequence.
Suggested reviewers: quattordici
Merge Risk: 
Minimal · up to 9edab
-
No actionable compatibility issue is established for the package update; it is mergeable after normal checks.
Pre-merge checks: 
5
-
Full details: Title check
-
Explanation
The title names the change: a dependency bump of the Imposter NuGet package to 1.0.6. The raw summary confirms the only change is the centrally managed Imposter version in Directory.Packages.props, moving from 1.0.5 to 1.0.6. The title matches the main change and is specific. The objectives describe Explicit mode behavior changes in that release, which the title does not mention, but a dependency title does not need to cover release notes.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the package line,
The version steps to six in time.
One small update joins the stack,
A tidy number on the track.
The rabbit hops, then checks it twice.
Comment @coderabbitai help to get the list of available commands.
[Low impact] This dependency update appears safe to merge. SummaryUpdates
Reviews (1) · Last reviewed commit: "chore(deps): update dependency imposter ..." · Reviewed by Greptile |
This PR contains the following updates:
1.0.5→1.0.6Release Notes
themidnightgospel/Imposter (Imposter)
v1.0.6: Explicit mode requires a configured outcomeCompare Source
Fixes
In
Explicitmode, a call needs a setup with a configured outcome (#428, closes #396). Verifying a void method withCalledorCallCountregistered a bare setup, and that setup allowed its calls, so verification switched strictness off for the arguments it matched. The same held for a property or indexerSetter(...)that was only selected or verified. Now onlyReturns,ReturnsAsync,Throws,ThrowsAsync,UseBaseImplementation, orCallbackon a void method allows a call; a setter counts once it has aCallbackorUseBaseImplementation.Implicitmode is unchanged.Behaviour change: code that relied on a bare void setup or a bare
Setter(...)to allow calls inExplicitmode now getsMissingImposterException. Configure an empty callback instead, for exampleimposter.Log(Arg<int>.Any()).Callback(_ => { });.In
Implicitmode, a verification-only setup of a generic method for a compatible type argument, such asAddItem<object>(Arg<object>.Any()).Called(...), no longer catches laterAddItem<string>calls. They are recorded understring, as they are when no setup exists.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.