eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Upgrade Transmission to 4.1.1 #282

Merged
eblume merged 2 commits from feature/transmission-review into main 2026-03-04 07:44:33 -08:00
Conversation 0 Commits 2 Files changed 5 +9 -5
eblume commented 2026-03-04 07:39:22 -08:00
Owner
Copy link

Summary

  • Upgrade Transmission from 4.0.6-r4 to 4.1.1-r1
  • Uses Alpine edge community repo for transmission packages, keeping stable alpine:3.22 base
  • Fix stale image reference in service doc (was linuxserver, now custom registry image)
  • Mark transmission as reviewed in service-versions.yaml

Context

Service review found Transmission two minor versions behind (4.0.6 → 4.1.1). Alpine 3.22 only packages 4.0.6, so transmission is installed from edge's community repo with an exact version pin.

4.1.0 added improved µTP performance, IPv6/dual-stack UDP tracker, JSON-RPC 2.0 API. 4.1.1 is a bugfix release (20+ fixes).

Dagger test build passed locally.

Deployment and Testing

  • Build container via Forgejo workflow (mise run container-build-and-release transmission)
  • Update kustomization.yaml with new image tag
  • argocd app set torrent --revision feature/transmission-review && argocd app sync torrent
  • Verify web UI at https://torrent.ops.eblu.me
  • Check Grafana Transmission dashboard still receives metrics
  • After merge: argocd app set torrent --revision main && argocd app sync torrent

Note

The transmission-exporter sidecar (OOMKilling every ~30min, 294 restarts) is being tracked separately as a future replacement project.

## Summary - Upgrade Transmission from 4.0.6-r4 to 4.1.1-r1 - Uses Alpine edge community repo for transmission packages, keeping stable alpine:3.22 base - Fix stale image reference in service doc (was linuxserver, now custom registry image) - Mark transmission as reviewed in service-versions.yaml ## Context Service review found Transmission two minor versions behind (4.0.6 → 4.1.1). Alpine 3.22 only packages 4.0.6, so transmission is installed from edge's community repo with an exact version pin. 4.1.0 added improved µTP performance, IPv6/dual-stack UDP tracker, JSON-RPC 2.0 API. 4.1.1 is a bugfix release (20+ fixes). Dagger test build passed locally. ## Deployment and Testing - [ ] Build container via Forgejo workflow (`mise run container-build-and-release transmission`) - [ ] Update kustomization.yaml with new image tag - [ ] `argocd app set torrent --revision feature/transmission-review && argocd app sync torrent` - [ ] Verify web UI at https://torrent.ops.eblu.me - [ ] Check Grafana Transmission dashboard still receives metrics - [ ] After merge: `argocd app set torrent --revision main && argocd app sync torrent` ## Note The transmission-exporter sidecar (OOMKilling every ~30min, 294 restarts) is being tracked separately as a future replacement project.
- Update Dockerfile to pull transmission 4.1.1-r1 from Alpine edge
  community repo while keeping stable alpine:3.22 base
- Fix service doc image reference (was linuxserver, now custom image)
- Mark transmission as reviewed in service-versions.yaml

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit b460333da0 into main 2026-03-04 07:44:33 -08:00
eblume referenced this pull request from a commit 2026-03-04 07:44:35 -08:00
Upgrade Transmission to 4.1.1 (#282)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!282
No description provided.