Skip to content
This repository was archived by the owner on Aug 23, 2026. It is now read-only.

Bump livery 0.6.1 + barrel_mcp 2.3.0; un-skip 3 body-drain smoke tests - #67

Merged
benoitc merged 1 commit into
mainfrom
bump/livery-0.6
Jul 19, 2026
Merged

benoitc merged 1 commit into
mainfrom
bump/livery-0.6

Conversation

@benoitc

@benoitc benoitc commented Jul 19, 2026

Copy link
Copy Markdown
Member

Summary

  • livery 0.6.x forwards max_body_size to h1's parser (sets it to infinity, enforces max_body in livery_body). Bodies over h1's 8 MiB default no longer trip a parser-level client_reset before livery's cap + drain engage.
  • Un-skips 3 body-drain smoke tests (accepts_body_above_cowboy_default_length, messages_413_returns_request_too_large_type, responses_413_returns_request_too_large_type).
  • Widens livery_service:listener_opts() to include max_body, so the dialyzer suppression on start_listener/0 is dropped.
  • Bumps barrel_mcp to 2.3.0 so its h2/hackney constraints align with livery 0.6.1.

Bumps: livery 0.4.4 -> 0.6.1, barrel_mcp 2.2.4 -> 2.3.0, h2 0.10.2 -> 0.11.0, hackney 4.4.5 -> 4.7.2, quic 1.6.5 -> 1.7.1.

livery 0.6.x forwards `max_body_size' to h1's parser (sets it to
infinity and enforces `max_body' in livery_body), so bodies over
h1's 8 MiB default no longer trip a parser-level client_reset
before livery's own cap + drain engage. Un-skips:

  accepts_body_above_cowboy_default_length
  messages_413_returns_request_too_large_type
  responses_413_returns_request_too_large_type

Also widens livery's listener_opts type to include `max_body', so
the dialyzer suppression on start_listener/0 is no longer needed.

barrel_mcp bumped to 2.3.0 to align its h2/hackney constraints with
livery 0.6.1 (2.2.4 pinned older h2/hackney, blocking resolution).

Bumps: livery 0.4.4 -> 0.6.1, barrel_mcp 2.2.4 -> 2.3.0,
h2 0.10.2 -> 0.11.0, hackney 4.4.5 -> 4.7.2, quic 1.6.5 -> 1.7.1.
@benoitc
benoitc merged commit e079da3 into main Jul 19, 2026
18 checks passed
@benoitc
benoitc deleted the bump/livery-0.6 branch July 19, 2026 21:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant