From 45fae9952aaccc9e41fc785cf835c4d45bd2a7bb Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Sun, 3 May 2026 13:51:55 +0000 Subject: [PATCH] chore(deps): remove stale go-jose v4.0.4 entries from go.sum MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Follow-up to f68fd00 (the go-jose v4.0.4 → v4.1.4 upgrade). The upgrade commit's `go mod tidy` ran out of disk in the sandbox before it could finish writing the cleaned go.sum back, leaving 2 stale v4.0.4 entries alongside the new v4.1.4 entries. CI's `go mod tidy && git diff --exit-code go.mod go.sum` flagged the drift on the next push (PR #410): -github.com/go-jose/go-jose/v4 v4.0.4 h1:... -github.com/go-jose/go-jose/v4 v4.0.4/go.mod h1:... This commit removes those 2 lines so go.sum holds only v4.1.4 hashes. Verified locally: - grep "go-jose" go.sum → only v4.1.4 lines. - go build ./internal/api/acme/ → clean. - go test -count=1 -short ./internal/api/acme/ → 16-case JWS suite green. --- go.sum | 2 -- 1 file changed, 2 deletions(-) diff --git a/go.sum b/go.sum index be7d9b0..215b2f2 100644 --- a/go.sum +++ b/go.sum @@ -141,8 +141,6 @@ github.com/ghodss/yaml v1.0.0/go.mod h1:4dBDuWmgqj2HViK6kFavaiC9ZROes6MMH2rRYeME github.com/go-gl/glfw v0.0.0-20190409004039-e6da0acd62b1/go.mod h1:vR7hzQXu2zJy9AVAgeJqvqgH9Q5CA+iKCZ2gyEVpxRU= github.com/go-gl/glfw/v3.3/glfw v0.0.0-20191125211704-12ad95a8df72/go.mod h1:tQ2UAYgL5IevRw8kRxooKSPJfGvJ9fJQFa0TUsXzTg8= github.com/go-gl/glfw/v3.3/glfw v0.0.0-20200222043503-6f7a984d4dc4/go.mod h1:tQ2UAYgL5IevRw8kRxooKSPJfGvJ9fJQFa0TUsXzTg8= -github.com/go-jose/go-jose/v4 v4.0.4 h1:VsjPI33J0SB9vQM6PLmNjoHqMQNGPiZ0rHL7Ni7Q6/E= -github.com/go-jose/go-jose/v4 v4.0.4/go.mod h1:NKb5HO1EZccyMpiZNbdUw/14tiXNyUJh188dfnMCAfc= github.com/go-jose/go-jose/v4 v4.1.4 h1:moDMcTHmvE6Groj34emNPLs/qtYXRVcd6S7NHbHz3kA= github.com/go-jose/go-jose/v4 v4.1.4/go.mod h1:x4oUasVrzR7071A4TnHLGSPpNOm2a21K9Kf04k1rs08= github.com/go-logr/logr v1.2.2/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A=