Skip to content

Releases: boringSQL/dryrun

v0.8.3

30 May 13:52

Choose a tag to compare

What's Changed

  • fix: index validity not being captured by @radim in #34

Full Changelog: v0.8.2...v0.8.3

v0.8.2

29 May 20:25
93e72b2

Choose a tag to compare

What's Changed

  • feat: distribute dryrun via npm with prebuilt platform binaries by @radim in #33

Full Changelog: v0.8.1...v0.8.2

v0.8.1

29 May 07:56

Choose a tag to compare

Full Changelog: v0.8.0...v0.8.1

v0.8.0

28 May 20:02

Choose a tag to compare

Back to Go
First of all if somebody is reading it - I have to admit the "boring" policy was broken. While DryRun started as Go project, somewhere around v0.4 - v0.5, it got as proof-of-concept re-written in Rust. It felt exiting. While it was good experience it's not worth for project like DryRun, I have 10+ years experience with Go. While using Rust on and off, I had very often moments where I had to turn to LLM and ask - explain me why this does not work. I like core Rust, not the async story. Plus dependency problems with boringSQL ecosystem started causing issues.

Data Masking has been #1 requested feature. Given the similar logic in Fixturize it was obvious choice to implement something that can be re-used across boringSQL stack.

You can get started with MASKING-TUTORIAL.md.

Background work on snapshot store enables new features and uses proper versioning for upcoming schema migrations. Some improvements already made it to v0.8. Strict separation of schema / planner / activity snapshots is now reality.

MCP improvements

  • dropped refresh_schema - pending #10
  • adopted MCP metadata - _meta.next replaces _meta.hint

Other fixes

  • Fixed handling of replicas
  • and many smaller fixes

What are current most pressing issues

  • Support for multiple DBs per project (done on backend, pending for MCPs to use) - #7
  • As the design of the DryRun taking shape; No MCP tool to use production database connection is being done (parts already in v0.8.0), but proper cleanup is needed. There MUST not be any path that can allow it. Nor suggest it. #24
  • Major imporvements to Snapshot diff functionality #30

and much more. Please, follow https://github.com/boringSQL/dryrun/issues to stay up to date, or signup for boringSQL newsletter https://boringsql.com/newsletter/

And as always, feel free to reach out if you have any comments/questions about the project. Mail to radim@boringsql.com

Full Changelog: v0.7.1...v0.8.0

v0.7.1

14 May 06:28

Choose a tag to compare

Fixed COALESCE on pg_get_function_result; lack of it made introspection to longer fail (silently to make it worse).

Download dry_run_cli 0.7.1

File Platform Checksum
dry_run_cli-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
dry_run_cli-x86_64-apple-darwin.tar.xz Intel macOS checksum
dry_run_cli-x86_64-pc-windows-msvc.zip x64 Windows checksum
dry_run_cli-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
dry_run_cli-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

v0.7.0

12 May 20:30

Choose a tag to compare

What's new

This release brings several improvement behind the scene. But the main feature is ability to push/pull the snapshots to/from shared storage.

To publish the snapshots you need

cd project_name

# capture from the live DB (use cwd name for project name)
dryrun init --db "$DATABASE_URL"
dryrun snapshot take --db "$DATABASE_URL"
dryrun snapshot push --to-path ./snapshots --all

Developers can then import the snapshots to the local history

dryrun snapshot pull --from-path ./shared/snapshots --all

Download dry_run_cli 0.7.0

File Platform Checksum
dry_run_cli-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
dry_run_cli-x86_64-apple-darwin.tar.xz Intel macOS checksum
dry_run_cli-x86_64-pc-windows-msvc.zip x64 Windows checksum
dry_run_cli-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
dry_run_cli-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum