set version to 0.39.4 (release #108 readTimeout)#113
Closed
ClaydeCode wants to merge 1 commit into
Closed
Conversation
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>
Contributor
Author
|
Redundant — main is already at 0.39.4 and the 0.39.4 release is published/built. Closing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bump version
0.39.3 → 0.39.4to 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 tag0.39.3(2026-06-05) predates it, so no shard runs the readTimeout (#111). This bump is the precursor to publishing the0.39.4GitHub Release, whichrelease.ymlbuilds intoghcr.io/freeshardbase/freeshard:0.39.4.Follow-up (not in this PR)
0.39.4GitHub Release (maintainer action) → triggers the image build.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.11bump (controller #322), since v2.11 (Go 1.25) self-raises the nofile ceiling. readTimeout still usefully reaps abandoned connections.🤖 Generated with Claude Code