Skip to content

chore(deps): update jwx/v3 to v3.1.1#175

Closed
JAORMX wants to merge 1 commit into
mainfrom
chore/jwx-v3.1.1
Closed

chore(deps): update jwx/v3 to v3.1.1#175
JAORMX wants to merge 1 commit into
mainfrom
chore/jwx-v3.1.1

Conversation

@JAORMX
Copy link
Copy Markdown
Collaborator

@JAORMX JAORMX commented May 28, 2026

Summary

Bumps github.com/lestrrat-go/jwx/v3 from v3.0.13 to v3.1.1 plus the transitive bumps that come with it.

This replaces the Renovate-opened #166, which was closed earlier while we evaluated a v3→v4 migration. The migration was rejected: jwx v4 requires GOEXPERIMENT=jsonv2 process-wide (encoding/json/v2 is still a Go experiment), and the operational footprint — every build, every CI workflow, every dev shell, plus the program-wide json semantics change — outweighed the perf win for our JWT verification path. Revisit when json/v2 is promoted to stable or jwx ships a v1-build-tag fallback.

Reopening #166 wasn't possible — Renovate deletes the source branch on PR close, so GitHub rejects the reopen. Same diff, different branch name.

Test plan

  • task test — all packages pass
  • task lint — 0 issues
  • task build — server builds clean
  • CI on this PR is green

Mechanical Renovate-style bump from v3.0.13 to v3.1.1. Picks up the
transitive bumps of decred/dcrd/secp256k1/v4 (4.4.0 → 4.4.1),
goccy/go-json (0.10.3 → 0.10.6), and golang.org/x/sys (0.39.0 → 0.43.0)
that come with it.

Replaces the closed #166. Reopen failed because Renovate deletes the
source branch on close; this is the same diff under a different branch
name.

Staying on v3 deliberately for now — v4 requires GOEXPERIMENT=jsonv2
process-wide (encoding/json/v2 is still an experiment), and the
operational footprint outweighs the perf win for our use case. Revisit
when json/v2 is promoted to stable or jwx ships a v1 build-tag fallback.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
@JAORMX JAORMX closed this May 28, 2026
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