chore(deps): update hex dependencies (patch)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
credo (source)	dev	patch	1.7.13 → == 1.7.15
ecto_sql (source)	prod	patch	3.13.2 → == 3.13.4
ex_aws_s3 (source)	prod	patch	2.5.8 → == 2.5.9
oban (source)	prod	patch	2.20.1 → == 2.20.2
phoenix_live_reload (source)	dev	patch	1.6.1 → == 1.6.2
phoenix_live_view (source)	prod	patch	1.1.17 → == 1.1.19

---

Release Notes

rrrene/credo (credo)

v1.7.15

Compare Source

• Improve performance on large projects
• Parse token_metadata for source files
• Credo.Check.Warning.ExpensiveEmptyEnumCheck have better issue messages
• Credo.Check.Refactor.MatchInCondition add new param :allow_operators
• Credo.Check.Refactor.MatchInCondition fix false positive
• Credo.Check.Readability.AliasOrder fix false positive
• Credo.Check.Readability.FunctionNames fix false positive
• Credo.Check.Readability.SinglePipe add new param :allow_blocks (defaults to true)
• Credo.Check.Refactor.ModuleDependencies fix false positive

v1.7.14

Compare Source

• Fix regression for DuplicatedCode
• Expand Credo.Check.Warning.ExpensiveEmptyEnumCheck to cover less obvious cases
• New Check: Credo.Check.Warning.StructFieldAmount

elixir-ecto/ecto_sql (ecto_sql)

v3.13.4

Compare Source

Bug fixes

• [mysql] Do not crash mix ecto.load with large dumped databases

v3.13.3

Compare Source

Enhancements

• [sql] Tag generated functions as :generated
• [sql] Add :wrap_in_transaction option to explain

Bug fixes

• [mysql] Fix structure_load/2 for MySQL 9.4+

ex-aws/ex_aws_s3 (ex_aws_s3)

v2.5.9

Compare Source

oban-bg/oban (oban)

v2.20.2

Compare Source

Enhancements

• [Telemetry] Add domain to attach_default_logger metadata

  Although this information is present in the source attribute, it’s not part of the metadata,
  it’s part of the attributes. And when encode = true, it’s generated as a string, which makes
  it less convenient to work with.

• [Cron] Add unique cron entry identifiers to job meta

  A id value is generated for each cron entry and stored in the job's meta to distinguish between
  different cron jobs with the same expression.

Bug Fixes

• [Stager] Order staging query to maximize compound index usage

  The core compound index couldn't be utilized by staging queries when the planner estimated a
  large number of hits. Changing the query to order by scheduled_at and id, it becomes an
  index scan.

  It would still be more efficient to use a dedicated index, but OSS doesn't have any mechanisms
  for automatic concurrent index creation and we have to save it for later.

• [Executor] Take measurements from the executing process

  When Producer starts jobs, it calls Executor.new in its own process, before handing it off to
  Task.Supervisor.async_nolink to call Executor.call. That means it used the Producer pid,
  and took measurements from that process.

• [Oban] Set scheduled state correctly when updating with update_job/3

  When the scheduled_at timestamp is set during update_job, the state is automatically set to
  scheduled. This mirrors the functionality of insert_job.

  Note that the value of the timestamp isn't considered. Setting a timestamp in the past will set
  the job as scheduled. This isn't a problem in practice because the stager will change the
  state to available on the next cycle anyhow.

• [Repo] Include :deadlock_detected in expected errors

  Deadlocks are automatically resolved by Postgres because it aborts one transaction. At that
  point, the retry should succeed quickly since the blocking transaction is gone.

phoenixframework/phoenix_live_reload (phoenix_live_reload)

v1.6.2

Compare Source

• Bug fixes
  • Properly deal with Unicode when forwarding logs

phoenixframework/phoenix_live_view (phoenix_live_view)

v1.1.19

Compare Source

v1.1.18

Compare Source

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/New_York, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.