fix: drop easyjson dependency; bump Go to 1.24.0 #2108
Merged
+130
−141
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexandear
commented
Dec 3, 2025
alexandear
force-pushed
the
fix/remove-easyjson
branch
from
72b3355 to
b912c66
Compare
Contributor
Author
|
I don't know why security/snyk (swaggo) is failing, because I don't have access to the logs. |
ubogdan
approved these changes
Dec 3, 2025
Contributor
|
@alexandear Thansk fro your contribution! |
pborgen
pushed a commit
to pborgen/swag
that referenced
this pull request
Jan 8, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the PR
Bumps https://github.com/go-openapi/spec from v0.20.4 to v0.22.1. This automatically removes the
mailru/easyjsondependency and updates the Go version to1.24.0.Relation issue
Fixes #1857
Closes #1876
Additional context
Changes: go-openapi/spec@v0.20.4...v0.22.1
The tests changed slightly because the
securitysection is now placed afterresponsesin thespec.