changelog: remove mention of native backend's hashing scheme

The change in hashing scheme should not even be noticeable, except
maybe because the same objects may be saved twice and take extra
space, and may be slower because we compare the contents for equality
instead of short-circuiting when we the hash matches.
This commit is contained in:
Martin von Zweigbergk 2022-12-03 09:34:52 -08:00 committed by Martin von Zweigbergk
parent 8222ba94cf
commit d3dffe933c

View file

@ -29,11 +29,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
automatically upgraded the first time you run a command in an existing repo.
The operation IDs will change in that process.
* The hashing scheme for the native backend has changed. Unlike the operation
log, it will *not* be automatically upgraded. We consider the native backend
a proof-of-concept that users should not use. However, existing repos should
still be usable.
### New features
* Commands with long output are paginated.