Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented May 9, 2021

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/json-iterator/go require patch v1.1.10 -> v1.1.12

Release Notes

json-iterator/go

v1.1.12: fix go 1.18 compatibility

Compare Source

v1.1.11: bug fix

Compare Source

  • Fixed json iter doesn't work properly with nil RawMessage #​469
  • Fixed null in number json tag string (#​480)
  • Fixed errors during reading integers from chunked io.Reader #​477
  • Fixed nil pointer panic when Unmarshal with a empty file #​508
  • Fixed [float string]different result vs origin after call Marshal & Unmarshal #​510

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title fix(deps): update module github.com/json-iterator/go to v1.1.11 fix(deps): update module github.com/json-iterator/go to v1.1.12 Oct 18, 2021
@renovate renovate bot force-pushed the renovate/github.com-json-iterator-go-1.x branch from 4d3cd89 to 6228533 Compare October 18, 2021 18:10
@renovate
Copy link
Author

renovate bot commented Mar 23, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

2 participants