Skip to content

chore(release-next): release 3.0.0-alpha.4#40

Open
github-actions[bot] wants to merge 1 commit into
release-nextfrom
release-please--branches--release-next
Open

chore(release-next): release 3.0.0-alpha.4#40
github-actions[bot] wants to merge 1 commit into
release-nextfrom
release-please--branches--release-next

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

3.0.0-alpha.4 (2026-06-13)

Features

  • docs: Add 'When to Use' page and nav link (bd5c6f3)

Bug Fixes

  • client: bound HTTP/1.1 request body pump with outbound flush backpressure (c76e9ee)
  • client: stamp cancellation token into request options before channel enqueue (28d422d)
  • h3: dispose decoded frames and copy blocked QPACK header blocks (e51ab5d)
  • http2: stop returning in-use body-drain buffers to the shared pool on teardown (19b83c5)
  • server: guard buffered body fast path and serve single-segment bodies zero-copy (3358b02)
  • server: remove response data-rate entry when body completes (61a4b1e)
  • server: serialize HTTP/1.x pipelined dispatch and fix WirePipeliningSpec under-read (3429403)

Performance

  • h3: decode inbound frames zero-copy from the transport buffer (1171012)
  • server: deduplicate data-rate timer scheduling and reuse response pipe writer (0c0e157)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot force-pushed the release-please--branches--release-next branch from 011de09 to 4ff73d1 Compare June 13, 2026 07:49
@st0o0 st0o0 force-pushed the release-please--branches--release-next branch from 4ff73d1 to 01aab43 Compare June 13, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants