0.14.0

What's Changed

• chore: release 0.14.0
• fix: push releases with a deploy key (#163)
• remote: fix metadata refresher lifetime and stale token recovery (#138)
• feat: add a manually triggered release workflow (#160)
• docs: add supported feature matrices to the readmes (#161)
• docs: add a worked HTTPS reverse proxy example (#162)
• fix: load the napi binding lazily-failing (#159)
• fix: deflake the queue delivery e2e test (#158)
• fix: match native Deno.Kv.list selector validation (#157)
• fix: sync generated protobuf ts files with the datapath schema (#152)
• fix: add missing AtomicOperation.mutate() types (#122)
• feat: export KvU64 from the npm package (#156)
• fix: send content-type header on data path requests (#151)
• fix: report failed check indexes in AtomicWriteOutput (#150)
• chore: test the napi package on node 22 and 24 (#155)
• feat: build and publish the napi package for linux arm64 (#154)
• fix: build the darwin-x64 napi binary for the right architecture (#153)
• chore: use chrono::DateTime::from_timestamp in utc_now (#128)
• chore: upgrade prost to 0.14 (#149)
• chore: upgrade rusqlite to 0.40 (#148)
• chore: update env_logger to 0.11 and constant_time_eq to 0.5 (#147)
• chore: upgrade reqwest to 0.13 (#146)
• chore: upgrade axum to 0.8 (#145)
• chore: migrate to aws-sdk v1 (#144)
• chore: update Rust toolchain to 1.96.0 (#143)
• chore: fix prettier lint errors in napi test file (#142)
• chore: update npm/napi yarn.lock to address security advisories (#141)
• chore: update Cargo.lock to address security advisories (#140)
• chore: use correct version for denokv crate (#134)

Full Changelog: 0.13.0...0.14.0

0.7.0

What's Changed

• feat: multi-thread reads and batched writes by @losfair in #56
• feat: atomic sum on v8 values by @losfair in #53
• 0.7.0 by @losfair in #61

Full Changelog: 0.6.1...0.7.0

0.6.1

What's Changed

• Bypass npm build for changes in unrelated workflows by @johnspurlock-skymethod in #44
• Update npm readme, and export limited V8 serializer. by @johnspurlock-skymethod in #46
• More readme updates. by @johnspurlock-skymethod in #47
• Deep links for homepage and repository in npm package.json. by @johnspurlock-skymethod in #48
• 0.6.1 by @igorzi in #50

Full Changelog: 0.6.0...0.6.1

0.6.0

What's Changed

• New @deno/kv npm package. by @johnspurlock-skymethod in #39
• 0.6.0 by @igorzi in #42
• Constrain docker.yml publish to n.n.n tags only by @johnspurlock-skymethod in #43

Full Changelog: 0.5.0...0.6.0

0.6.0-next.1

0.6.0 (#42)

0.5.0

What's Changed

• feat: kv.watch support by @lucacasonato in #26
• feat: append versionstamp to key by @losfair in #40
• 0.5.0 by @losfair in #41

Full Changelog: 0.4.0...0.5.0

0.4.0

What's Changed

• fix: add cargo.toml description by @lucacasonato in #22
• docs: fix docker image in fly.io instructions by @lucacasonato in #23
• docs: add diagram in readme by @lucacasonato in #24
• add links by @lambtron in #25
• fix examples in README.md for --sqlite-path by @john-pope in #29
• Fix local kv protobuf response content-type by @johnspurlock-skymethod in #30
• Fix typo in kv connect protocol doc by @johnspurlock-skymethod in #31
• fix: set correct status code for non-U64 sums by @lucacasonato in #33
• chore: make SqliteMessageHandle methods public by @igorzi in #35
• fix(sqlite): don't unwrap in requeue_message by @igorzi in #37
• 0.4.0 by @igorzi in #38

New Contributors

• @lambtron made their first contribution in #25
• @john-pope made their first contribution in #29
• @johnspurlock-skymethod made their first contribution in #30

Full Changelog: 0.2.0...0.4.0

0.2.0

What's Changed

• refactor: extract datapath/interface converters by @igorzi in #19
• feat: s3 replica and pitr by @losfair in #17

New Contributors

• @igorzi made their first contribution in #19

Full Changelog: 0.1.0...0.2.0

0.1.0

feat: add standalone SQLite backed denokv server (#14)

This is a standalone Deno KV server backed by SQLite. It exposes a HTTP
API that implements the KV Connect protocol and can be used from
the Deno CLI.

The server can be connected to from multiple clients at the same time,
which enables a simple way to self host a production ready Deno KV
database.