Closed renovate[bot] closed 1 week ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 80.37%. Comparing base (
30efad7
) to head (2bffba5
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x
releases. But if you manually upgrade to 4.x
then Renovate will re-enable minor
and patch
updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
^3.0.0
->^4.0.0
Release Notes
jsonpickle/jsonpickle (jsonpickle)
### [`v4.0.0`](https://redirect.github.com/jsonpickle/jsonpickle/blob/HEAD/CHANGES.rst#v400) [Compare Source](https://redirect.github.com/jsonpickle/jsonpickle/compare/v3.4.2...v4.0.0) \====== \* **Breaking Change**: Python 3.7 is no longer supported. \* **Breaking Change**: Support for pre-0.7.0 `repr`-serialized objects is no longer enabled by default. The `safe` option to `decode()` was changed from `False` to `True`. Users can still pass `safe=False` to `decode()` in order to enable this feature for the purposes of loading older files, but beware that this feature relies on unsafe behavior through its use of `eval()`. Users are encouraged to re-pickle old data in order to migrate away from the the unsafe loading feature. (+514) \* The pickler no longer produces `py/repr` tags when pickling modules. `py/mod` is used instead, as it is clearer and uses one less byte. (+514) \* The test suite no longer uses the deprecated `datetime.datetime.utcnow()` function. (+539) ### [`v3.4.2`](https://redirect.github.com/jsonpickle/jsonpickle/blob/HEAD/CHANGES.rst#v342) [Compare Source](https://redirect.github.com/jsonpickle/jsonpickle/compare/v3.4.1...v3.4.2) \====== \* The breaking changes from v4 were inadvertedly included in v3.4.1, which has been yanked. This release remedies this by reverting the v4 changes. ### [`v3.4.1`](https://redirect.github.com/jsonpickle/jsonpickle/blob/HEAD/CHANGES.rst#v341) [Compare Source](https://redirect.github.com/jsonpickle/jsonpickle/compare/v3.4.0...v3.4.1) \====== \* Support decoding pandas dataframes encoded with versions 3.3.0 and older. (+536) ### [`v3.4.0`](https://redirect.github.com/jsonpickle/jsonpickle/blob/HEAD/CHANGES.rst#v340) [Compare Source](https://redirect.github.com/jsonpickle/jsonpickle/compare/v3.3.0...v3.4.0) \====== \* Officially support Python 3.12 in the GitHub Actions testing matrix, and update GHA package versions used. (+524) \* Improve reproducibility of benchmarking commands on Linux by using taskset and adding a "HOWTO" run benchmarks section in `benchmarking/README.md`. (+526) \* The `setup.cfg` packaging configuration has been replaced by `pyproject.toml`. (+527) \* `yaml` is now supported as a jsonpickle backend. (+528) \* `OSSFuzzConfiguration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.