Skip to content

fix(deps): upgrade s3proxy to 4.2.1 - #115

Merged
gmoon merged 1 commit into
mainfrom
fix/s3proxy-4.2.1
Jul 14, 2026
Merged

fix(deps): upgrade s3proxy to 4.2.1#115
gmoon merged 1 commit into
mainfrom
fix/s3proxy-4.2.1

Conversation

@gmoon

@gmoon gmoon commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Bumps the bundled s3proxy dependency ^4.2.0^4.2.1 (lockfile 4.2.04.2.1).

4.2.1 is a docs-only s3proxy release (no functional change vs 4.2.0), so the image behavior is identical — but rebuilding against it makes /version report 4.2.1 and keeps the published forkzero/s3proxy image in lockstep with the library.

fix: so release-please cuts a matching 4.2.1 image release; merging the resulting release PR builds + pushes forkzero/s3proxy:4.2.1 / :4.2 / :latest.

🤖 Generated with Claude Code

s3proxy 4.2.1 is a docs-only release (no functional change vs 4.2.0), but
rebuilding the image against it makes /version report 4.2.1 and keeps the
published forkzero/s3proxy image in lockstep with the library. A `fix:`
so release-please cuts a matching 4.2.1 image release.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gmoon
gmoon merged commit 05be502 into main Jul 14, 2026
3 checks passed
@gmoon
gmoon deleted the fix/s3proxy-4.2.1 branch July 14, 2026 19:20
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