chore(deps): update dependency imposter to 0.2.23

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Imposter	nuget	patch	0.2.21 → 0.2.23

---

Release Notes

themidnightgospel/Imposter (Imposter)

v0.2.23: Targets nested in generic types

Compare Source

Fixes

• Targets nested in generic types (#​362, closes #​337). A target registered open inside a generic type, such as typeof(Outer<>.Inner), got an imposter that referred to the containing type's type parameters without declaring them (CS0246). The imposter now declares them, outermost first, followed by the target's own type parameters, with their constraints, so Outer<T>.Inner<U> gets InnerImposter<T, U>. A closed registration such as typeof(Outer<int>.Inner) keeps its own imposter and can sit beside the open one. The generics docs cover it with an executable example.

v0.2.22: Keyword member names, allows ref struct collisions, imposter-named type parameters

Compare Source

Fixes

• Members named with escaped keywords (#​363, closes #​359). A member declared with an escaped keyword name, such as @class, @event or @object, was written bare in the imposter and failed to compile. Such names are now escaped wherever generated code uses them.
• Same-signature methods that differ only in allows ref struct (#​365, closes #​356). Two interfaces' methods with the same signature, where only one type parameter allows ref structs, got two implicit implementations (CS0111, CS0425). They're now implemented explicitly, like methods whose constraints differ in other ways.
• A type parameter named like the imposter class (#​366, closes #​354). A target such as IService<IServiceImposter> generated class IServiceImposter<IServiceImposter> (CS0694). The imposter keeps its name, and the type parameter takes another one in generated code.

Documentation

• Member types from other source generators (#​367). A member whose type another source generator produces keeps working: the type is written through and binds in the final compilation, as long as it's referenced fully qualified. An event whose delegate type comes from another generator is left out of the imposter. Its workaround is documented, and regression tests cover both cases.

Maintenance

• The generator dropped some dead code and renamed a check (#​360, #​361). Generated output is unchanged.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-12T17:43:43.845295Z	18551d8	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7fa046e0-3294-4630-9ddb-7618207a082b

---

📥 Commits

Reviewing files that changed from the base of the PR and between 0b63027 and 18551d8.

---

📒 Files selected for processing (1)

• Directory.Packages.props

---

🚧 Files skipped from review as they are similar to previous changes (1)

• Directory.Packages.props

---

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 6 remain after this review.

---

---

📝 Walkthrough

📝 Walkthrough

📝 Walkthrough

Walkthrough

The centrally managed Imposter package version changed from 0.2.21 to 0.2.23.

Changes

Imposter package update

Layer / File(s)	Summary
Update Imposter version Directory.Packages.props	The centrally managed Imposter package version changed from 0.2.21 to 0.2.23.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

---

Merge Risk: ⚪ Minimal · up to 18551

No actionable issue is established for this dependency update; it is mergeable after normal checks.

Pre-merge checks | 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage		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…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the package dependency update from Imposter 0.2.21 to 0.2.23.

---

✨ 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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{A rabbit checks the package row,
The version takes a step to go.
From twenty-one to twenty-three,
A tidy change for all to see.
I nibble carrots, then hop free!}

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

[High impact] The dependency update appears safe to merge; no blocking issue was found.

Summary

Updates Imposter from 0.2.21 to 0.2.23 in Directory.Packages.props.

• The benchmark project now uses Imposter 0.2.23.

_{Reviews (2) · Last reviewed commit: "chore(deps): update dependency imposter ..." · Reviewed by Greptile}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 18551d80b0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Pin Imposter to the reviewed 0.2.22 release

This selects 0.2.23 even though the commit title, dependency-update table, and included release notes all scope the change as 0.2.21 → 0.2.22. Consequently, restoring TUnit.Mocks.Benchmarks pulls a release whose changes were not presented for review; either use 0.2.22 here or regenerate the update metadata and review the 0.2.23 changes.

Useful? React with 👍 / 👎.