Skip to content

chore: 0.49.2 - #558

Merged
7schmiede merged 1 commit into
mainfrom
chore/0.49.2
Nov 17, 2026
Merged

7schmiede merged 1 commit into
mainfrom
chore/0.49.2

Conversation

@7schmiede

Copy link
Copy Markdown
Member

What and why

Release 0.49.2, the fix of #556 (#557): a static service's forward and the hub's way to its daemons keep their connections instead of one per request.

  • Version 0.49.2 in Cargo.toml (cargo update -w) and ui/package.json/package-lock.json.
  • CHANGELOG.md: [0.49.2] - 2026-11-17 with its summary; compare links.
  • docs/plan.md: status line and the §7.4 paragraph.
  • devstack.toml: reviewed = "0.49.2"; devstack check clean.

Checked

  • Windows: on fix(static): a forward keeps its connections to the target (#556) #557, 2000 requests through serve-static --forward open 4 connections to the target (0.49.1: 2001), cargo test --workspace; here the dashboard gate (audit-shipped.mjs) after npm run build, cargo deny … advisories, scripts/release-notes.sh 0.49.2.
  • Linux and macOS: CI only; nothing platform-specific changed.
  • No code or security review report covers v0.48.0..HEAD (owner's choice for this release series).

🤖 Generated with Claude Code

Fixed: a static service's `forward` keeps its connections to the target
instead of opening one per request, which drained the ephemeral ports on
Windows under an end-to-end suite; the hub keeps its connections to the
daemons the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@7schmiede
7schmiede merged commit cc863a7 into main Nov 17, 2026
14 checks passed
@7schmiede
7schmiede deleted the chore/0.49.2 branch November 17, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant