Skip to content

Feat: Add support for InMemoryRedisSetCache#91

Closed
robert-mihaiAdam wants to merge 2 commits into
mainfrom
feat/add_inmemory_set_cache
Closed

Feat: Add support for InMemoryRedisSetCache#91
robert-mihaiAdam wants to merge 2 commits into
mainfrom
feat/add_inmemory_set_cache

Conversation

@robert-mihaiAdam

@robert-mihaiAdam robert-mihaiAdam commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Changes

  • Add support for InMemory and InMemoryRedis set cache

Test plan

  • Unit tests added/updated
  • Integration tests pass locally (dotnet test)
  • CHANGELOG.md updated

Linked issues

Fixes #

Contributor declaration

  • I signed off my commits per the DCO (git commit -s).
  • I am contributing on behalf of my employer, or in the course of employment / using employer resources. (If checked, your employer may hold IP rights in this work, which can require a signed CLA — a maintainer will follow up. See CONTRIBUTING.md.)

@robert-mihaiAdam
robert-mihaiAdam force-pushed the feat/add_inmemory_set_cache branch 2 times, most recently from 9727644 to e7445f8 Compare July 20, 2026 12:32
Signed-off-by: robert-mihaiAdam <robert.adam@uipath.com>
@github-actions

Copy link
Copy Markdown

🔎 Maintainer heads-up: automated triage flagged this PR as potentially material, so it may need a signed CLA in addition to the DCO sign-off.

Strong signals

  • adds public API surface (PublicAPI.Unshipped.txt in src/UiPath.Caching.Queue)
  • changes shipped public API — possible removal/breaking change (PublicAPI.Shipped.txt in src/UiPath.Caching.Queue)
  • adds dependency: Microsoft.Extensions.Caching.Memory

Other signals

  • large production change (+987 lines under src/)

Context

  • external contributor (CONTRIBUTOR) with a substantial change (+987 lines under src/)

This is advisory only — the bot does not decide. Please judge against the CLA criteria (material, product-critical, patent-sensitive, corporate contributor, broad commercial use). Note that thresholds can be gamed by splitting PRs, so use your judgement.

  • If a CLA is needed → add the cla-required label (a contributor comment with signing steps is posted automatically).
  • If it is not needed → replace needs-cla-review with cla-not-required so later pushes don't re-flag it.

@github-actions github-actions Bot added the needs-cla-review A maintainer should assess whether a signed CLA is required (see CONTRIBUTING.md) label Jul 20, 2026
@robert-mihaiAdam
robert-mihaiAdam marked this pull request as draft July 20, 2026 14:15
@robert-mihaiAdam robert-mihaiAdam self-assigned this Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-cla-review A maintainer should assess whether a signed CLA is required (see CONTRIBUTING.md)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant