chore(deps-minor) Update dependency redlock to "~> 2.1.0"

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
redlock	"~> 2.0.6" → "~> 2.1.0"

---

Release Notes

leandromoreira/redlock-rb (redlock)

v2.1.0: Support redis-client and redis transparently

Compare Source

• #​160 Thanks to @​corsonknowles
• drop support for older ruby version 2.5 and 2.6

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend,before 5am every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

[lago-claude-ai-agent]

Automated pre-review (advisory, not a required check) — verdict: HOLD · CI green

HOLD — The changed Gemfile line still says Redlock is pinned to 2.0.x because it is locally patched, but the constraint now targets 2.1.x and that Redlock patch no longer exists.

• Remove or rewrite the stale pin rationale so it matches the current dependency and code.

[lago-claude-ai-agent]

Automated pre-review (advisory, not a required check) — verdict: HOLD · CI green

HOLD: Update the Gemfile comment alongside the version bump: ~> 2.1.0 pins Redlock to 2.1.x, so the current claim that it is pinned to 2.0.x is false.

[lago-claude-ai-agent]

Automated pre-review (advisory, not a required check) — verdict: PASS · CI green

PASS — The Redlock and lockfile updates are compatible with activejob-uniqueness and the existing Redis client integration; existing uniqueness specs cover the affected locking paths.

Non-blocking: update the Gemfile comment, which still says Redlock is pinned to 2.0.x although the constraint now targets 2.1.x.