chore(deps): bump oban from 2.23.0 to 2.23.1

[dependabot]

Bumps oban from 2.23.0 to 2.23.1.

Changelog

Sourced from oban's changelog.

v2.23.1 - 2026-08-02

Bug Fixes

• [Peer] Scope lease renewal to the owning node

  Leadership renewal matched the peers row by name alone, so a node that lost its lease renewed whichever row it found and concluded it was still the leader. The belief never corrected, letting a second node run Cron and insert duplicate jobs until restart.

  Renewal is now scoped to the row's owner, so a peer that lost the lease demotes at the next election. Failed elections concede leadership rather than retaining it, and no longer crash the peer.

• [Producer] Dispatch on refresh for missed notifications

  When an insert notification is dropped a queue could sit idle until it was manually paused and resumed. Producers now attempt a dispatch on each refresh, so a stuck queue self-heals on the next cycle. The default refresh_interval is now 60s (was 30s), since it purely controls recovery time.

• [Job] Set successful state as default unique options

  Use the complete successful group as the unique default so it includes the suspended state.

• [Reindexer] Reindex every configured index even when one fails

  A single missing or invalid index previously halted the entire reindex run, silently skipping every index after it. Each reindex is now independent, and failures are aggregated into the run's telemetry error metadata, identifying exactly which queries failed.

• [Migration] Fix custom migrator resolution

  Use the repo selected from opts[:repo] when resolving a configured custom migrator.

Commits

• f86cc92 Release v2.23.1
• 7d96854 Scope peer lease renewal to the owning node
• f92c53e Dispatch on refresh for missed notifications
• 581bdcb Expand unique state groups for unique: true
• 52cd08e Fix custom migrator resolution (#1483)
• a772915 Set successful state in default unique options (#1463)
• 4e06067 Reindex every configured index even when one fails
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[hyperpolymath]

Closing auto-generated PR as part of nuclear cleanup. Will be recreated fresh from current state if still needed.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.