Skip to content

set version to 0.39.4 (release #108 readTimeout)#113

Closed
ClaydeCode wants to merge 1 commit into
mainfrom
chore/version-0-39-4
Closed

set version to 0.39.4 (release #108 readTimeout)#113
ClaydeCode wants to merge 1 commit into
mainfrom
chore/version-0-39-4

Conversation

@ClaydeCode

Copy link
Copy Markdown
Contributor

What

Bump version 0.39.3 → 0.39.4 to cut a release.

Why

#108 (fix(traefik): set finite readTimeout on entrypoints) merged to main on 2026-06-21 but is in no released image — latest tag 0.39.3 (2026-06-05) predates it, so no shard runs the readTimeout (#111). This bump is the precursor to publishing the 0.39.4 GitHub Release, which release.yml builds into ghcr.io/freeshardbase/freeshard:0.39.4.

Follow-up (not in this PR)

  1. Publish the 0.39.4 GitHub Release (maintainer action) → triggers the image build.
  2. Bump the controller core-version compose to freeshard:0.39.4 (a small follow-up to core v18 / a v19).

Note

This is now defence-in-depth, not the primary fix: the fd-exhaustion root cause is addressed by the traefik v2.6 → v2.11 bump (controller #322), since v2.11 (Go 1.25) self-raises the nofile ceiling. readTimeout still usefully reaps abandoned connections.

🤖 Generated with Claude Code

Cuts a release containing #108 (finite entrypoint readTimeout) so shards finally
get the abandoned-connection reaping. The fix has been merged on main since
2026-06-21 but is in no released image (latest tag 0.39.3 predates it), so no
shard runs it (#111).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ClaydeCode

Copy link
Copy Markdown
Contributor Author

Redundant — main is already at 0.39.4 and the 0.39.4 release is published/built. Closing.

@ClaydeCode ClaydeCode closed this Jun 24, 2026
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