Skip to content

dreamd v1.0.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Oct 15:12
· 71 commits to main since this release
v1.0.1
00e682d

Security

  • Dependency updates for new RustSec advisories, Cargo.lock only: rustls 0.23.46 (RUSTSEC-2026-0346, 0347, 0348, 0349), rustls-webpki 0.103.16 (RUSTSEC-2026-0382), webpki-root-certs 1.0.10 (RUSTSEC-2026-0383), webpki-roots 1.0.10 (RUSTSEC-2026-0381), quinn-proto 0.11.19 (RUSTSEC-2026-0338, 0340, 0343).

Changed

  • dreamd setup ends its success card with one line naming the repository: Source, docs, issues: https://github.com/botzrDev/dreamd.
  • The npm package dreamd-mcp describes what dreamd does instead of calling itself a shim, adds keywords, homepage and bugs, and its README opens with a repository link.
  • The README's sample transcript is replaced by a live recording (docs/assets/demo.gif, tape in docs/assets/demo.tape): Claude Code saves a lesson, OpenCode recalls it. The dreamOS pointer paragraph moved to a "Where dreamd fits" section near the end, text unchanged.

Fixed

  • Public pages and a few printed strings now match the 1.0.0 tree. SPEC.md describes prefix clustering, a cycle timestamp on last_updated, and single-writer append. The HTTP stability note no longer points at v0.2. Windows health is described as a watermark read. The WasTrue section is a scaffold. dream, init, and migrate help, the auto-mode errors, the npm Windows error, and the WORKSPACE.md scaffold line no longer cite v0.1 or v0.2.
  • dreamd watch prints the same auto-mode sentence as dreamd dream. The config template comment matches docs/configuration.md. dreamd mcp on Windows says to start dreamd watch first. dreamd uninstall and dreamd update on Windows say they do not stop the daemon. SPEC.md says the reference reader stores evt_ plus 26 Crockford characters and skips other id spellings, including UUIDv7.
  • Windows dreamd init registers the project: registry.toml is locked with File::lock and replaced by a temp-file rename. io::write_atomic stays unsupported, so the dream cycle and the Tantivy index still do not run. dreamd memory checkout and bisect refuse a live Windows daemon (a loopback connect to server.json) and still refuse a Unix socket file that merely exists.
  • The GitHub v1.0.0 binaries and the npm dreamd-mcp@1.0.0 tarball still print the older v0.1 / v0.2 sentences (watch auto mode, --auto, WORKSPACE.md, the Windows MCP and shim errors). The 1.0.1 binaries and npm package are built from this tree and carry the corrected strings.

SHA-256 checksums

ebab544ace8f8f36812db4288489bfc95298ea60124fe36dc2a9fc71f69bedfa  dist/darwin-aarch64.tar.gz/darwin-aarch64.tar.gz
d283b5ee2b3572ad2996457aa1c36ae79c028d0cdf88c6454d05c20c35a6bed0  dist/darwin-x86_64.tar.gz/darwin-x86_64.tar.gz
ff5e6c4f19c5d9017be0847eb6fb9e81d0fd4c67ff1961cb0635d5aadaef3288  dist/linux-x86_64-musl.tar.gz/linux-x86_64-musl.tar.gz
b6ab30ed36a6e62dedf2a5e3c406eac3e384dea3e27e7fd93a5e36bd1029cdb4  dist/linux-x86_64.tar.gz/linux-x86_64.tar.gz
848c007a2070e672d9165480e4a075f2d98aa7683108da44fea1ff9f8329bb78  dist/windows-x86_64.tar.gz/windows-x86_64.tar.gz
Assets 9
Loading