fix(deps): update module github.com/buger/jsonparser to v1.3.0 - #106
Merged
Conversation
|
➡️ Go test coverage stayed the same at 83.0% compared to 4432c18
No change in coverage for any package. View coverage for all packages# Package Name | Coverage
+ github.com/Depado/gin-auth-example | 83.0% |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v1.2.0→v1.3.0Release Notes
buger/jsonparser (github.com/buger/jsonparser)
v1.3.0Compare Source
Formally verified by ReqProof
jsonparser v1.3.0 is the first Go library proven to L3 assurance by ReqProof, a git-native requirements-engineering and formal-verification platform. The entire codebase is now covered by:
encoding/jsondifferential harnesses.The proof review found and fixed 7 real bugs that years of community use, OSS-Fuzz, and standard fuzzing had missed. Read the root-cause analysis →
jsonparser serves as the reference case study for ReqProof — learn more at reqproof.com.
Security / bug fixes
Fix Delete panic on malformed input with leading comma (OSS-Fuzz
4649128)Deletepanicked withindex out of range [-1]on inputs like,{"test":1{}.The
data[prevTok]dereference is now guarded.Fix empty-string key-component panics (8 sites)
Get,GetString,GetInt,GetFloat,GetBoolean,GetUnsafeString,Set,Delete,EachKeypanicked withindex out of range [0]when a key path containedan empty string (
""). All 8 unguardedkeys[i][0]dereference sites are now guardedwith
len(...) > 0. Found by the structure-aware hazard sweep.Reported by @c-tonneslan (#284).
Fix Set data loss on scalar arrays (#267)
Seton an array-index path beyond the current length silently overwrote the arrayinstead of appending.
Set({"a":[1,2,3]}, 99, "a", "[9]")now returns{"a":[1,2,3,99]}instead of
{"a":[99]}. Reported by @Solaris-star (#286).Fix Set malformed-JSON output on cross-type paths
Setwith an array-index path component under an object parent (e.g.Set({}, 9, "[5]"))produced invalid JSON (
{[9]}). Set now auto-coerces the container type to match thepath, always producing valid JSON output.
Fix Delete trailing-comma malformation
Deleteleft a dangling trailing comma in the output when the deleted element wasfollowed by JSON whitespace (space/tab/LF/CR) and a comma. Found by the structure-aware
path-mutation fuzzer.
Fix ArrayEach spurious callback on non-array root
ArrayEachon a non-array root value (e.g.ArrayEach({"a":1}, cb)) invoked thecallback with a spurious element before returning an error. The callback is no longer
invoked; a clean error is returned immediately.
Fix lone-Unicode-surrogate mishandling in Unescape
ParseStringon a string containing a lone high surrogate (e.g.\uDB29without afollowing low surrogate) synthesized a bogus non-BMP code point from the following
literal bytes. Now substitutes U+FFFD (matching
encoding/jsonbehavior).Performance
parseInt fast-path for short numbers — 22–37% faster on typical 1–10 digit integers.
Numbers with ≤18 digits use direct int64 accumulation, bypassing the overflow-checked
uint64 slow path. Contributed by @trevorprater (#285).
stringEnd SIMD fast path — 12× faster on no-escape strings, 4.5× faster end-to-end
on
Getfor string values. Usesbytes.IndexBytefor the common case (no\beforethe closing
").Acknowledgments
4649128) — the original Delete leading-comma panicConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.