v3.0.0-RC2
This commit is contained in:
parent
478160ed85
commit
e3c1d478d1
3 changed files with 20 additions and 9 deletions
25
CHANGELOG.md
25
CHANGELOG.md
|
|
@ -1,5 +1,16 @@
|
|||
> This project uses [Break Versioning](https://github.com/ptaoussanis/encore/blob/master/BREAK-VERSIONING.md) as of **Aug 16, 2014**.
|
||||
|
||||
## v3.0.0-RC2 / 2020 Sep 12
|
||||
|
||||
```clojure
|
||||
[com.taoensso/nippy "3.0.0-RC2"]
|
||||
```
|
||||
|
||||
#### New since `v3.0.0-RC1`
|
||||
|
||||
- Serializable: add `allow-and-record-any-serializable-class-unsafe` util.
|
||||
|
||||
|
||||
## v3.0.0-RC1 / 2020 Sep 11
|
||||
|
||||
```clojure
|
||||
|
|
@ -15,35 +26,35 @@
|
|||
|
||||
Note that there's separate documentation below if upgrading from `v2.15` or `v2.14`:
|
||||
|
||||
## Since `v2.15.0` (incl. BREAKING changes)
|
||||
### Since `v2.15.0` (incl. BREAKING changes)
|
||||
|
||||
See [#130] for **detailed upgrade instructions**.
|
||||
|
||||
### Changes
|
||||
#### Changes
|
||||
|
||||
- **[BREAKING]** Bumped minimum Clojure version from `v1.5` to `v1.7`.
|
||||
- **[BREAKING]** `*serializable-whitelist*` has been split into two separate vars: `*freeze-serializable-allowlist*`, `*thaw-serializable-allowlist`*. See [#130] for details.
|
||||
- **[BREAKING]** `:nippy/unthawable` responses now have a standardized form: `{:nippy/unthawable {:type _ :cause _ ...}`. Most folks won't care about this change unless you have code specifically to deal with `:nippy/unthawable` responses.
|
||||
- By default, `freeze` now allows the use of Java's Serializable for any class. `thaw` continues to be restrictive by default, and will quarantine any objects not on the class allowlist. See [#130] for details.
|
||||
|
||||
### New
|
||||
#### New
|
||||
|
||||
- [#122] Option to disable freezing and/or thawing of metadata.
|
||||
- `freeze` and `thaw` now support opts: `:serializable-allowlist`, `:incl-metadata?`.
|
||||
- New `read-quarantined-serializable-object-unsafe!` util to read quarantined Serializable objects. See [#130] for details.
|
||||
|
||||
## Since `v2.14.0` (incl. BREAKING changes)
|
||||
### Since `v2.14.0` (incl. BREAKING changes)
|
||||
|
||||
See [#130] for **detailed upgrade instructions**.
|
||||
|
||||
### Changes
|
||||
#### Changes
|
||||
|
||||
- **[BREAKING]** [#130] `thaw` will now quarantine Serializable objects whose class is not allowed by `*thaw-serializable-allowlist*`. See [#130] for details.
|
||||
- **[BREAKING]** Bumped minimum Clojure version from `v1.5` to `v1.7`.
|
||||
- **[BREAKING]** `:nippy/unthawable` responses now have a standardized form: `{:nippy/unthawable {:type _ :cause _ ...}`. Most folks won't care about this change unless you have code specifically to deal with `:nippy/unthawable` responses.
|
||||
- [#101] Switch default encryptor from `AES-CBC` to `AES-GCM` (faster, includes integrity check)
|
||||
|
||||
### New
|
||||
#### New
|
||||
|
||||
- [#127] Add utils: `freeze-to-string`, `thaw-from-string` (@piotr-yuxuan)
|
||||
- [#113 #114] Add support for object arrays (@isaksky)
|
||||
|
|
@ -51,7 +62,7 @@ See [#130] for **detailed upgrade instructions**.
|
|||
- [#83 #113] Add support for URIs (@isaksky)
|
||||
- [#126] `extend-freeze`: include id collision odds in docstring
|
||||
|
||||
### Fixes
|
||||
#### Fixes
|
||||
|
||||
- [#120] Update `freezable?` to cover `nil`
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
**[CHANGELOG]** | [API] | current [Break Version]:
|
||||
|
||||
```clojure
|
||||
[com.taoensso/nippy "3.0.0-RC1"] ; BREAKING, see CHANGELOG for details
|
||||
[com.taoensso/nippy "3.0.0-RC2"] ; BREAKING, see CHANGELOG for details
|
||||
[com.taoensso/nippy "2.15.3"] ; BREAKING, see CHANGELOG for details
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
(defproject com.taoensso/nippy "3.0.0-RC1"
|
||||
(defproject com.taoensso/nippy "3.0.0-RC2"
|
||||
:author "Peter Taoussanis <https://www.taoensso.com>"
|
||||
:description "High-performance serialization library for Clojure"
|
||||
:url "https://github.com/ptaoussanis/nippy"
|
||||
|
|
|
|||
Loading…
Reference in a new issue