Skip to content

chore: bump github.com/spf13/viper from 1.19.0 to 1.21.0#74

Merged
SyniRon merged 1 commit into
developfrom
chore/viper-bump
May 19, 2026
Merged

chore: bump github.com/spf13/viper from 1.19.0 to 1.21.0#74
SyniRon merged 1 commit into
developfrom
chore/viper-bump

Conversation

@SyniRon

@SyniRon SyniRon commented May 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

Direct bump of github.com/spf13/viper from 1.19.0 → 1.21.0.

In-repo viper usage (cmd/root.go, servers/server.go, cmd/serve.go) is limited to AutomaticEnv() + GetString(...), so the indirect-dep churn introduced by 1.21 is inert for us:

  • Dropped: hashicorp/hcl, magiconair/properties, mitchellh/mapstructure (config-format libs we don't use)
  • Added: go-viper/mapstructure/v2 (replacement; not invoked through our code paths)

Transitively bumped

  • fsnotify v1.8.0 → v1.9.0
  • pelletier/go-toml/v2 v2.2.3 → v2.2.4
  • sagikazarmark/locafero v0.7.0 → v0.11.0
  • spf13/afero v1.12.0 → v1.15.0
  • spf13/cast v1.7.1 → v1.10.0

Test plan

  • go build ./... clean
  • go vet ./... clean
  • make generate produces no proto/*.pb.go drift
  • Local docker-compose smoke against XF mirror after merge — auth (both bearer casings), cache HIT/MISS, tickets categories endpoint

Supersedes #65.

🤖 Generated with Claude Code

Direct bump only; usage in this repo is limited to AutomaticEnv() +
GetString(), so the indirect-dep churn (drops HCL / properties /
mitchellh-mapstructure; adds go-viper/mapstructure/v2) is inert.

Transitively pulled forward:
- fsnotify v1.8.0 → v1.9.0
- pelletier/go-toml/v2 v2.2.3 → v2.2.4
- sagikazarmark/locafero v0.7.0 → v0.11.0
- spf13/afero v1.12.0 → v1.15.0
- spf13/cast v1.7.1 → v1.10.0

Verified locally: go build ./... clean, go vet ./... clean,
make generate produces no proto/*.pb.go drift.

Supersedes #65.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@SyniRon
SyniRon merged commit db4993d into develop May 19, 2026
2 checks passed
@SyniRon
SyniRon deleted the chore/viper-bump branch May 19, 2026 23:56
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