chore(deps): update dependency imposter to 0.2.10

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Imposter	nuget	patch	0.2.8 → 0.2.10

---

Release Notes

themidnightgospel/Imposter (Imposter)

v0.2.10: Ref struct indexer keys

Compare Source

Features

• Indexer keys of a custom ref struct type (#​297, part of #​201). A key of a ref struct type, passed by value, no longer reports IMP009. An imposter can't keep or match a ref struct key, so it passes the key through:
  • Setups and verification match the other keys only, as in imposter[Arg<int>.Any()].Getter().Returns((row, locator) => row + locator.Offset).
  • The delegates passed to Returns, Callback and Throws, and the base implementation, get the key.
  • The default behaviour keeps a value set by the other keys, whatever the ref struct key.
  • An indexer whose keys are all ref structs, or whose other keys are another indexer's, is set up by a method named after it, such as imposter.Indexer() or imposter.Indexer_1(). Its interface's setup view declares the same method.

Still IMP009 (see Limitations):

• a ref struct indexer key taken by in;
• a class indexer of a ref struct type with an in or ref readonly key and a base getter;
• a ref struct whose type uses a method's type parameters;
• a ref struct argument of an async event;
• type parameters that allow ref structs;
• a span returned by reference.

v0.2.9: Custom ref struct members, and generated name clashes

Compare Source

Features

Members with a custom ref struct type, part of #​201. These no longer report IMP009. An imposter can't keep or match a ref struct, so it only passes one between the caller and your delegates:

• Methods with ref struct parameters (#​286).
  • Setups and verification take matchers for the other parameters only, and the invocation history leaves the argument out.
  • The delegates passed to Returns, Callback and Throws, and the base implementation, get the argument, by reference for ref and out.
  • Overloads that differ only in their ref struct parameters get numbered setups, such as Read_1.
• Methods that return a ref struct (#​287).
  • Returns takes only a delegate, as in Returns(size => new Slot(size)).
  • The invocation history doesn't record the result.
  • Without a setup, the method returns default.
• Events whose delegate takes a ref struct (#​288). Raise passes it on to the callbacks and the handlers, and Raised matches the other arguments.
• Properties of a ref struct type (#​290, #​292).
  • The getter's Returns takes only a delegate.
  • Setter() takes no criteria, and Called counts every set.
  • Without a setup, a class property reads its base getter each time, and any other property returns default.
• Indexers of a ref struct type (#​296).
  • The getter's Returns takes only the delegate that gets the keys.
  • The setter's history and Called leave the value out.
  • Without a setup, the getter returns the base getter's value or default.

Still IMP009 (see Limitations):

• a ref struct indexer key;
• a class indexer of a ref struct type with an in or ref readonly key and a base getter;
• a ref struct whose type uses a method's type parameters;
• a ref struct argument of an async event;
• type parameters that allow ref structs;
• a span returned by reference.

Fixes

• Generated types named like another member (#​293, closes #​289). The imposter declares types named after each member, such as ICurrentPropertyBuilder or GetDelegate. Two cases made the imposter fail with CS0102:

  • a target member named like one of those types;
  • two members whose names derive the same type name, such as Foo and FooCallback.

  The member whose types clash now names them after another unique name. Its setup keeps its name.

• Event and indexer builder fields named like another member (#​295, closes #​294). A property named _Changed next to an event Changed, or _IndexerIndexer next to an indexer, failed with CS0102. Those fields now avoid the other members' names, as a property's already did.

---

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-10T14:41:32.893019Z	da2a512	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: fb249de7-58e1-46fc-9558-274a221346b1

---

---

---

📥 Commits

Reviewing files that changed from the base of the PR and between c1fc146 and da2a512.

---

---

---

📒 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 changes from 0.2.8 to 0.2.10.

Changes

Imposter package update

Layer / File(s)	Summary
Update managed package version Directory.Packages.props	The centrally managed Imposter package version changes from 0.2.8 to 0.2.10.

Priority: ⬇️ Low

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

Change: Other

---

---

---

---

Merge Risk: ⚪ Minimal · up to da2a5

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 main change: updating the Imposter dependency to version 0.2.10.

---

✨ 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,
“Two ten,” it reads, “the version’s fine.”
The props file holds the updated tag,
No extra changes in its bag.
Then off it hops through fields of green.}

_{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.8 to 0.2.10 in Directory.Packages.props.

• Projects now use Imposter 0.2.10 through the shared version list.

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

ℹ️ 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.9 release

The commit title, dependency table, and included release notes all describe reviewing an upgrade from 0.2.8 to 0.2.9, but this line actually selects 0.2.10. As a result, consumers build against a different, otherwise unreviewed release; either pin this to 0.2.9 or update the change metadata and validation to cover 0.2.10.

Useful? React with 👍 / 👎.