Release Notes¶
1.2.2 (2026-04-08)¶
Bug Fixes¶
1.2.1 (2026-04-07)¶
Bug Fixes¶
1.2.0 (2026-04-07)¶
This release introduces project-wide ignore files. A new .weevr/ignore
file — or equivalently a .weevrignore at the project root — lets you exclude
scratch folders, drafts, editor backups, and anything else you don't want the
CLI to treat as part of your project. The patterns apply to every command that
walks the project tree: weevr validate, weevr list, weevr deploy, and
weevr status. Both files use gitignore-style syntax and are optional; when
both exist, their patterns are unioned with no precedence ordering.
The problem this solves is small but sharp. Until now, the only ignore
mechanism was .weevr/deploy-ignore, which only affected deploy and
status. A scratch/ folder with half-finished drafts or deliberately broken
YAML would be picked up by weevr validate, flagged as orphans by
weevr list, and could even fail validation outright — and there was no way
to say "this folder is not part of the project" without literally deleting
the files. Now you can:
# .weevr/ignore
# Scratch folder for in-progress work
scratch/
# Drafts and experiments
*.draft.thread
*.draft.weave
# Editor backups
*~
.DS_Store
Or, if you prefer the convention familiar from .gitignore and
.dockerignore, the same file can live at the project root as
.weevrignore. Use whichever location you prefer — or both, if you want to
keep personal patterns separate from shared ones.
Explicit target paths bypass the ignore filter. If you pass a specific
file or directory to weevr validate on the command line, it is validated
regardless of ignore patterns:
# Full-project scan — scratch/ is excluded by the ignore file
weevr validate
# Explicit path — bypasses the ignore filter, validates scratch/draft.thread
weevr validate scratch/draft.thread
# Same rule applies to directory targets
weevr validate scratch/
The rule is simple: if you named it on the command line, you meant it. The ignore filter applies only to the implicit full-project scan.
.weevr/deploy-ignore is deprecated and scheduled for removal in v1.3.0.
It is still honored by weevr deploy and weevr status during the deprecation
window, but every command that encounters it (validate, list, deploy,
status) prints a one-line deprecation warning on stderr directing you to
migrate. The warning is suppressed in --json mode so automation remains
clean. To migrate, move the patterns from .weevr/deploy-ignore into
.weevr/ignore (or .weevrignore) and delete the old file — the contents
are identical, only the filename and scope differ.
See Configuration › Ignore files for the full reference.
Features¶
1.1.4 (2026-04-07)¶
Bug Fixes¶
1.1.3 (2026-04-07)¶
Bug Fixes¶
1.1.2 (2026-04-07)¶
Bug Fixes¶
1.1.1 (2026-04-06)¶
Bug Fixes¶
1.1.0 (2026-04-06)¶
This release aligns the CLI with the weevr engine v1.13 release. The headline
addition is warp — a new artifact type for declaring target table schema
contracts. Warp files (.warp) define the intended shape of a target table:
columns, types, nullability, and key metadata. They're now a first-class citizen
across the CLI: weevr new warp scaffolds from a template, weevr validate
checks them against the bundled schema, and weevr deploy, weevr status, and
weevr list all recognize them.
The bundled thread and weave schemas have been updated to v1.13, picking up
support for thread parameterization (params on weave thread entries) and
instance aliasing (as for reusing the same thread ref multiple times in a
weave). The default schema version in new projects is now 1.13.
This release also fixes a validation issue where parameterized thread files
using ${param.*} or ${env.*} variable references in non-string fields (like
match_keys) were incorrectly rejected. The validator now recognizes bare
${...} references and skips static type checks on them, since those values are
resolved at runtime by the engine.
Features¶
Bug Fixes¶
1.0.0 (2026-04-03)¶
⚠ BREAKING CHANGES¶
- add documentation site and prepare v1.0 release (#19)
Features¶
0.1.8 (2026-04-03)¶
Features¶
0.1.7 (2026-04-03)¶
Features¶
0.1.6 (2026-04-03)¶
Features¶
0.1.5 (2026-04-03)¶
Features¶
Bug Fixes¶
0.1.4 (2026-04-03)¶
Bug Fixes¶
0.1.3 (2026-04-02)¶
Bug Fixes¶
0.1.2 (2026-04-02)¶
Features¶
- add embedded YAML templates for thread, weave, and loom files (c6803d6)
- add interactive wizard to init command (9db6cc9)
- cli: implement init and new commands with templates and interactive wizard (b71b16b)
- implement init command with project scaffolding (43c2ca4)
- implement new command for generating weevr files (8330864)
0.1.1 (2026-04-02)¶
Features¶
- add AppState dataclass for Typer context (c533363)
- add config dataclasses and YAML loading (dfd95a3)
- add global --json flag, config loading, and AppState to root callback (2273bd0)
- add output helpers for Rich and JSON modes (921ee11)
- cli: add CLI foundation with config loading, JSON output, and Rich diagnostics (1c3373f)
- project: scaffold weevr-cli repository (35d4fcd)
- read version from package metadata instead of hardcoded string (831f9f4)
Bug Fixes¶
- ci: add contents read permission to CodeQL workflow (a9a8707)
- ci: commit uv.lock for reproducible CI builds (edef632)
Documentation¶
- recommend uv over pipx for installation (bac8b41)