chore(deps): update elixir minor updates

[wttj-bot]

This PR contains the following updates:

Package	Type	Update	Change	Pending
ecto (source)	prod	minor	3.13.6 → 3.14.0	3.14.1
ecto_sql (source)	dev	minor	3.13.5 → 3.14.0
faker (source)	dev	minor	~> 0.12 → ~> 0.19
hackney (source)	prod	minor	4.4.5 → 4.5.2

---

Release Notes

elixir-ecto/ecto (ecto)

v3.14.0

Compare Source

Enhancements

• [Ecto.Adapter] Accept a counter option in prepare_query/3
• [Ecto.Changeset] Add Ecto.Changeset.reorder_assoc/2
• [Ecto.Query] Allow from and joins with {fragment, Schema} source
• [Ecto.Repo] Raise an error on query-like keyword opts to Repo functions
• [Ecto.Repo] Support :replace_changed on upserts to enable HOT updates in PostgreSQL
• [Ecto.Repo] Add :query_cache option to selectively bypass query cache
• [Ecto.Schema] Add :on_join_through_conflict option for
• [Ecto.Type] Add Ecto.Type.trim/2 and allow developers to configure how values are trimmed on cast with the :trim_values option
• [Ecto.UUID] Support UUIDv7
• [mix.exs] Require decimal v3
• [mix ecto.create] Set timezone by default when creating new databases

Bug fixes

• [Ecto.Repo] Correctly extract passwords with colons from URL
• [Ecto.Repo] Redact repo config from SASL progress reports
• [Ecto.Repo] Preload custom queries with order_by now take precedence over :preload_order. The :preload_order option is now only applied when no custom query with ordering is provided.

elixir-ecto/ecto_sql (ecto_sql)

v3.14.0

Compare Source

Enhancements

• [migrations] Allow table modifiers such as UNLOGGED tables
• [migrations] Add Safe Ecto Migration guides
• [mysql] Support insert_mode: :ignore
• [postgres] Set a default timezone on mix ecto.create
• [sandbox] Label the sandbox owner process
• [sql] Allow fragment tuple sources in adapters
• [sql] Allow pid repos in Ecto.Adapters.SQL.table_exists?
• [sql] Accept counter option in to_sql/4
• [sql] Support {:unsafe_fragment, ...} support to RETURNING clause

elixirs/faker (faker)

v0.19.0

Compare Source

benoitc/hackney (hackney)

v4.5.2: hackney 4.5.2

Compare Source

Dependency bump release. No API changes.

Changed

• Bump h2 to 0.10.4. It fixes a regression from 0.10.3 where a blocking send whose data had fully drained received {error, stream_closed} when the stream closed on its END_STREAM chunk. A waiting sender is now settled as ok once the send buffer has drained, and only gets the close-reason error when data is still outstanding.
• Bump quic to 1.7.0. Relevant to hackney's HTTP/3 client: the connection flow-control window now slides forward with received bytes instead of stalling after 8 MiB, so large HTTP/3 downloads keep flowing; the idle timer restarts on received activity per RFC 9000 §10.1; an invalid peer SETTINGS frame now closes the connection cleanly instead of crashing; and a client recognizes a server stateless reset (RFC 9000 §10.3) and closes promptly instead of waiting for the idle timeout.
• Bump webtransport to 0.4.3, which aligns its transitive h2 (0.10.4) and quic (1.7.0) dependencies with hackney's own, so the wt_* API runs on the same HTTP/2 and HTTP/3 stack versions.

v4.5.1

Compare Source

Changed

• Bump h2 to 0.10.3. It fixes an HTTP/2 upload hang: a sender blocked on
  flow control is now released with {error, stream_reset} or
  {error, stream_closed} when the peer cancels the stream, instead of
  hanging for the connection's lifetime. This affects hackney's streamed
  request bodies over HTTP/2 when the server resets the stream
  mid-backpressure.

v4.5.0

Compare Source

Added

• HTTP QUERY method (RFC 10008) as a first-class method: hackney:query/1..4
  helpers and hackney:request(query, ...). QUERY is safe and idempotent and
  carries a request body like POST. It works over HTTP/1.1, HTTP/2, and
  HTTP/3 with every request body mode (binary, streamed, async, connection
  API).

---

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.

👻 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 has been generated by Mend Renovate.

[wttj-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: mix.exs

Artifact update for ecto resolved to version 3.14.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 3.14.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/