v1.2.0

Full Changelog: v1.1.4...v1.2.0

v1.1.4

Full Changelog: v1.1.3...v1.1.4

v1.1.3

Full Changelog: v1.1.2...v1.1.3

v1.1.2

What's Changed

• harden: this pnpm workspace configuration does not set ... in... by @anupamme in #10

New Contributors

• @anupamme made their first contribution in #10

Full Changelog: v1.1.1...v1.1.2

v1.1.1

Full Changelog: v1.1.0...v1.1.1

v1.1.0-beta.3

Full Changelog: v1.1.0-beta.2...v1.1.0-beta.3

v1.1.0

What's Changed

• Phase 2: MCP server for the Vault effect registry by @hitesh-bhardwaj in #6
• Fix: CLI completely broken - restore missing getFileContent export by @hitesh-bhardwaj in #8
• Fix: vite.config.js auto-fixers silently break CommonJS configs by @hitesh-bhardwaj in #9

New Contributors

• @hitesh-bhardwaj made their first contribution in #6

Full Changelog: v1.0.77...v1.1.0

v1.1.0-beta.2

What's Changed

• Phase 2: MCP server for the Vault effect registry by @hitesh-bhardwaj in #6
• Fix: CLI completely broken - restore missing getFileContent export by @hitesh-bhardwaj in #8
• Fix: vite.config.js auto-fixers silently break CommonJS configs by @hitesh-bhardwaj in #9

New Contributors

• @hitesh-bhardwaj made their first contribution in #6

Full Changelog: v1.0.77...v1.1.0-beta.2

v1.0.77

Full Changelog: v1.0.76...v1.0.77

v1.0.76

Fixed

• add no longer overwrites existing files when only --yes is passed (data-loss safety fix). Previously, --yes (intended to skip interactive prompts) also silently permitted overwriting files already on disk, so re-running add <effect> --yes could replace a locally customized effect with the registry version, with no confirmation. --yes now only skips prompts; replacing existing files requires an explicit --overwrite. When files already exist and --overwrite is not passed, the existing files are left untouched and the effect is skipped with a clear message pointing at --overwrite and hyperiux diff.

Changed

• Behavior change for scripts and muscle-memory usage: any add … --yes invocation that relied on the old implicit-overwrite behavior will now skip existing files instead of replacing them. Add --overwrite to those commands to keep replacing files.
• add --dry-run now always shows its preview even when target files already exist (it no longer prompts or blocks on the overwrite check, since a dry run writes nothing).