Pin ArgoCD to v3.2.6 #44

Merged
eblume merged 2 commits from feature/pin-argocd-v3.2.6 into main 2026-01-22 16:38:28 -08:00
Owner

Summary

  • Pin ArgoCD kustomization to v3.2.6 tag instead of stable branch
  • This gives intentional control over ArgoCD version upgrades

Deployment and Testing

  • Sync the apps application: argocd app sync apps
  • Point argocd at feature branch: argocd app set argocd --revision feature/pin-argocd-v3.2.6
  • Sync argocd: argocd app sync argocd
  • Verify ArgoCD is running v3.2.6
  • After merge, reset to main: argocd app set argocd --revision main && argocd app sync argocd

🤖 Generated with Claude Code

## Summary - Pin ArgoCD kustomization to v3.2.6 tag instead of `stable` branch - This gives intentional control over ArgoCD version upgrades ## Deployment and Testing - [ ] Sync the `apps` application: `argocd app sync apps` - [ ] Point argocd at feature branch: `argocd app set argocd --revision feature/pin-argocd-v3.2.6` - [ ] Sync argocd: `argocd app sync argocd` - [ ] Verify ArgoCD is running v3.2.6 - [ ] After merge, reset to main: `argocd app set argocd --revision main && argocd app sync argocd` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Change from `stable` branch (which tracks latest) to explicit version tag.
This gives control over when ArgoCD upgrades happen.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- transmission: latest → 4.0.6 (torrent + kiwix sidecar)
- miniflux: latest → 2.2.16
- kubectl: latest → 1.34.1 (matches k8s server 1.34.0)
- tailscale proxy: stable → v1.92.5
- tailscale k8s-operator: stable → v1.92.5

devpi remains on :latest with a TODO comment as it's a custom-built
image that needs semantic versioning in the build process.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
eblume merged commit af39067e1f into main 2026-01-22 16:38:28 -08:00
eblume referenced this pull request from a commit 2026-01-22 16:38:28 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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!44
No description provided.