-
Couldn't load subscription status.
- Fork 104
Comparing changes
Open a pull request
base repository: go-jose/go-jose
base: v4.1.1
head repository: go-jose/go-jose
compare: v4.1.2
- 6 commits
- 19 files changed
- 7 contributors
Commits on Jul 17, 2025
-
Update go-jose documentation (#198)
- Remove CHANGELOG.md We haven't been good about keeping it up-to-date. Consult git history or Github Releases for change information Fixes #196 - Remove broken shields.io tests status. The test status shield isn't working. Consult the Github Actions output to see current test status. - Clarify different go-jose versions More aggressively recommend users migrate to Version 4, and include notes about encoding/json/v2 for the Version 5 of go-jose. Document that we will support the two current Golang releases on V4. Fixes #184 - Fixup markdown table borders
Configuration menu - View commit details
-
Copy full SHA for 6acb8e6 - Browse repository at this point
Copy the full SHA 6acb8e6View commit details -
Remove dependency on testify (#197)
This PR removes the dependency on testify. Unit tests of the new code are included. **Why remove testify:** - testify is a dependency (and has indirect dependencies) - testify uses go-spew which is not maintained anymore (see stretchr/testify#1638) - go-spew is in a 'not allowed' list in Kubernetes (see kubernetes/kubernetes#103942) and therefore kubernetes can't use go-jose v4 (see kubernetes/kubernetes#123252) - Equal was used to compare complex structs, but Equal in testify doesn't fully compare values, see stretchr/testify#1616 - removing testify would remove the dependencies on external projects, reducing operational risk, as go-jose has a lot of users --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Matthew McPherrin <mattm@letsencrypt.org> Co-authored-by: Jacob Hoffman-Andrews <github@hoffman-andrews.com>
Configuration menu - View commit details
-
Copy full SHA for 10dbdce - Browse repository at this point
Copy the full SHA 10dbdceView commit details -
jwk: list all missing fields on error (#195)
The switch statement is exited subsequent to the first condition that evaluates to true, yet it is evident from the context that the intention was to cover all possibilities. Found by PostgresPro Related: 98e5a54 ("Print all missing fields at once")
Configuration menu - View commit details
-
Copy full SHA for 6a17172 - Browse repository at this point
Copy the full SHA 6a17172View commit details -
jwk: JSONWebKey.UnmarshalJSON can return ErrUnsupportedKeyType (#191)
Ultimately we want to ignore unsupported key types in JSONWebKeySets (#26 / #130), but we are blocked on doing a breaking change release. In the meantime, we can have JSONWebKey (the singular version) return ErrUnsupportedKeyType. This allows users to write their own JWKS umarshalling method to ignore unsupported key types, eg. https://github.com/zitadel/oidc/blob/045b59e5a55be97ba180fdaae96fb66302a03353/pkg/client/rp/jwks.go#L221-L235.
Configuration menu - View commit details
-
Copy full SHA for e2cde04 - Browse repository at this point
Copy the full SHA e2cde04View commit details -
jwe: accept non-pointer JSONWebKey in Recipient (#200)
JSONWebKey is marked as a valid type in Recipient but was rejected further down the line when calling `makeJWERecipient()`.
Configuration menu - View commit details
-
Copy full SHA for 3a80e13 - Browse repository at this point
Copy the full SHA 3a80e13View commit details
Commits on Jul 18, 2025
-
testutils/assert: remove True, Nil, NotNil (#202)
These functions were used few places, and could generally be replaced with a simple `if` and a more informative error message, or a more specific assert function. Follow up to #197
Configuration menu - View commit details
-
Copy full SHA for a1565a4 - Browse repository at this point
Copy the full SHA a1565a4View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.1.1...v4.1.2