1.8.0 should have been 2.0.0

Question

1.8.0 should have been 2.0.0

stevenroussey-privicy opened this issue 5 years ago · 3 comments

stevenroussey-privicy commented 5 years ago

v1.8 switches to v4 file format, and v4 file format requires Argon2, thus a breaking change.

Answer 1 · 2020-06-06T19:08:17.000Z

Also, sample code for using node-argon2, sodium-native, and a wasm implementation would be great.

Answer 2 · 2020-06-06T19:12:47.000Z

Hi! KeeWeb has been supporting KDBXv4 for more than three years. Also we don't strictly follow semver and assign versions in more a common sense rather than breaking/non-breaking changes. So that a bigger change like whole UI or technology redesign would be 2.0, while small things like default file format no.

Answer 3 · 2020-06-06T19:14:08.000Z

Just realized that that issue is in kdbxweb, not keeweb. However same applies, KDBXv4 has been supported for a long time and it shouldn't be a breaking change.