Update jason 1.3.0 → 1.4.4 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ jason (1.3.0 → 1.4.4) · Repo · Changelog

Release Notes

1.4.1 (from changelog)

• Add limit to decoded integer sizes of 1024 digits. This can be changed with the decoding_integer_digit_limit app env config.

1.4.0

Enhancements

• Use the :erlang.float_to_binary(_, [:short]) function, instead of io_lib_format.fwrite_g/1
  where available (OTP 24.1+). This provides equivalent output with much less memory used
  and significantly improved performance.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 37 commits:

• Bump 1.4.4
• Raise if trying to decode decimals without decimal
• Remove unneeded workarounds for xref warnings
• Fix warnings by conditionally compiling Decimal support
• Bump 1.4.3
• Fix derive with _ key
• Require stream_data only from Elixir 1.12
• Bump 1.4.2
• Fix deprecation warnings in tests
• Update dependencies
• Format charlists
• Fix codegen to expand ranges
• Fix non-deterministic test on OTP27 (#187)
• Removes unused Dialyzer ignored warnings (#182)
• Remove uneeded backtick (#173)
• Bump 1.4.1
• Update dialyxir
• Fix tests on OTP 26
• Add CI for OTP 26 & Elixir 1.15
• Remove deprecated ubuntu-18 runner from CI
• Run CI in version branches
• Limit large inter decoding
• Document Jason.Fragment (#166)
• Try another way to fix CI
• Fix CI on old ubuntu
• Adjust CI os
• Bump CI deps
• Update README for version 1.4 (#157)
• Add a "Encoders" sub-section to README (#156)
• Release 1.4.0
• Bump bench deps
• Bump CI versions
• Bump deps
• Use float_to_binary [:short] if available
• Bump OTP version in GitHub Actions (#153)
• Update README.md (#152)
• fix release year (#146)

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)