chore: bump version in readme

Author: logseq-cldwalker

README.md

@@ -36,7 +36,7 @@ $ nbb-logseq -e '(+ 1 2 3)'
 
 ## Database Version
 
-To use `nbb-logseq` with [the database version](https://github.com/logseq/logseq#-database-version), specify the version as `logseq/nbb-logseq#feat-db-v29`. This version is only available through github and has not been released to npm. An npm version will be released when the database version has a desktop release.
+To use `nbb-logseq` with [the database version](https://github.com/logseq/logseq#-database-version), specify the version as `logseq/nbb-logseq#feat-db-v30`. This version is only available through github and has not been released to npm. An npm version will be released when the database version has a desktop release.
 
 Unlike file graphs, DB graphs can be written by scripts. This is powerful and opens up more use cases for scripting. To write your own script, you'll need a package.json and nbb.edn. Use [this example package.json](https://github.com/logseq/publish-spa/blob/feat/db/package.json) and [this example nbb.edn](https://github.com/logseq/publish-spa/blob/feat/db/nbb.edn). Some example database graph scripts:
 
@@ -163,4 +163,4 @@ Steps to publish a new npm package:
 1. Update CHANGELOG.md if anything specific to nbb-logseq has been updated.
 2. Update nbb with `bb update-nbb` on https://github.com/babashka/nbb-features and confirm CI passes.
   * This is done to confirm that datascript and datascript-transit tests pass.
-3. Update nbb with `bb update-nbb` on this repo and confirm CI passes.
+3. Update nbb with `bb update-nbb` on this repo and confirm CI passes.