[mchesterbot]

This PR contains the following updates:

Package	Type	Update	Change
bullmq (source)	dependencies	patch	6.5.0 → 6.5.3

---

Release Notes

taskforcesh/bullmq (bullmq)

v6.5.3

Compare Source

Bug Fixes

• node-redis: clear ended status when connect() reopens the client (#​4952) (0928d9f)

v6.5.2

Compare Source

Bug Fixes

• relay: format exclusive time bounds without precision loss (#​5043) (19ae429)

v6.5.1

Compare Source

Bug Fixes

• flow: defer parent release until all children are added (python) (elixir) (rust) (dotnet) (#​4988) fixes #​4944 (0e1a990)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 has been generated by Mend Renovate CLI.

[claude]

Claude finished @mchesterbot[bot]'s task in 11s —— View job

---

Review: Update dependency bullmq to v6.5.3

• Read the diff
• Checked it against package.json

Summary: This is a lockfile-only patch bump, 6.5.0 → 6.5.3. I found nothing blocking.

What changed

• package-lock.json: only the node_modules/bullmq entry changed (version, resolved URL, integrity hash). The cron-parser dependency line is the same as before.
• package.json is unchanged. Its range is ^6.3.16, which already allows 6.5.3.

Release notes (6.5.1 to 6.5.3)

• 6.5.1, flow: parent release is now deferred until all children are added. This fixes a race where a parent could run before its children were added. Look at this one if we use flows.
• 6.5.2, relay: time bounds are formatted without precision loss. This should not affect us.
• 6.5.3, node-redis: the ended status is cleared when connect() reopens the client. This only matters if we use the node-redis adapter. I didn't check that.

Risk by area

• Code quality and conventions: nothing to flag. There is no source change, so no CLAUDE.md conventions apply.
• Bugs: these are bug-fix releases only, with no breaking changes listed.
• Performance: no impact expected.
• Security: the integrity hash is the registry's, and I did not verify it. No new dependencies were added.
• Test coverage: no tests are added or needed. I did not run the unit or integration suites here. CI's Integration job, which uses Redis, is the check that exercises the queue code (Rewind, Stripe, watchlist sync, retention). Please confirm it is green before merging.

Automerge is disabled by config, so merge manually once CI passes.