[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Imposter	nuget	patch	0.2.17 → 0.2.19

---

Release Notes

themidnightgospel/Imposter (Imposter)

v0.2.19: Cross-kind name clashes, re-abstracted ref members, method type parameter names

Compare Source

Fixes

• Members that share a name across kinds (#​346, closes #​328). A target that gets a method, a property or an event of one name from different interfaces, such as a Current property and a Current() method, got an imposter that failed with CS0102. These members now take apart names on the imposter, like same-kind members already did. The target's own member names are unchanged.
• Re-abstracted ref-returning members (#​347, closes #​325). A ref-returning interface member with a default body that a derived interface re-abstracts left the target without an implementation. The imposter then failed with CS0535 and no diagnostic. Such a member is now handled like an abstract one: IMP011 is reported and no imposter is generated.
• Generic method type parameters named like the method's generated types (#​345, closes #​339). A method type parameter named like one of the types generated for its method made the imposter fail to compile. Examples are Get<GetDelegate>, Get<IGetMethodImposterBuilder> and Get<GetMethodImposterCollection> (CS0694, CS1503), and Get<Builder> or Get<Adapter> (CS0102). The method's generated types and nested classes now take other names in that case.

v0.2.18: Events whose type doesn't bind

Compare Source

Fixes

• Events whose type doesn't bind (#​341, closes #​320). An event whose delegate type couldn't be resolved, as happens in code being edited (for example System.Action shadowed by a type named System), or an event declared with a non-delegate type, made the generator report IMP005 and drop that target's imposter. With a Debug build of the generator, every imposter of the project was dropped. Such an event is now left out of the imposter, the compiler's own error stays the one to fix, and the rest of the imposter is generated.

---

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-12T10:02:32.557240Z	ce997a4	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: 19c943e9-f017-4e39-b30f-2c0deb8d51ae

---

📥 Commits

Reviewing files that changed from the base of the PR and between 5b01039 and ce997a4.

---

📒 Files selected for processing (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.17 to 0.2.19.

Changes

Imposter package update

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

Priority: ⬇️ Low

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

Change: Other

Suggested reviewers: quattordici

---

Merge Risk: ⚪ Minimal · up to ce997

This PR only updates the centrally managed Imposter version to 0.2.19. No concrete merge-blocking behavior is evident, so it is ready to merge subject to 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 identifies the dependency update from Imposter to version 0.2.19, which is the main change.

---

✨ 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 line,
The version hops ahead in time.
From seventeen to nineteen now,
A neat small change, the rabbit’s vow.
Soft paws tap the props file twice.}

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

[greptile-apps]

Confidence Score: 5/5

[Low impact] This dependency update appears safe to merge.

Summary

Updates Imposter from 0.2.17 to 0.2.19 in Directory.Packages.props.

• Projects using the central pin now get Imposter 0.2.19.

_{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: ce997a4215

ℹ️ 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]

Align the pinned Imposter version with the reviewed update

The commit title, dependency table, and release notes describe an update from 0.2.17 to 0.2.18, but this line actually selects 0.2.19. Version 0.2.19 is a separate upstream release with additional generator changes, so the benchmark project would consume code that was not represented in the dependency review; pin 0.2.18 or update the commit metadata and release notes to review 0.2.19 explicitly.

Useful? React with 👍 / 👎.