blockwatch-cli 0.15.0__tar.gz → 0.16.1__tar.gz

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/CHANGELOG.md

@@ -12,6 +12,51 @@ Releases up to and including v0.3.11 predate this file. Their notes live on the
 
 ## [Unreleased] - ReleaseDate
 
+## [0.16.1] - 2026-10-28
+
+### Added
+
+- Symbols in Go, C, C++, Python, Starlark, Rust, TypeScript and JavaScript files. `consts.go#/MaxPorts` points at a
+  top-level constant, variable, type or function, and `limits.h#/MAX_PORTS` at a macro. A value is the initializer as
+  written, such as `20 * 1024 * 1024`, so `same-as` can compare it with a constant in another file without a
+  `target-pattern`. A syntax error stops the run only for the names near it. See [Code files](docs/symbols.md#code-files),
+  [Go](docs/symbols.md#go), [C and C++](docs/symbols.md#c-and-c),
+  [Python and Starlark](docs/symbols.md#python-and-starlark), [Rust](docs/symbols.md#rust) and
+  [TypeScript and JavaScript](docs/symbols.md#typescript-and-javascript).
+
+## [0.16.0] - 2026-10-24
+
+### Changed
+
+- Without `same-as-pattern`, `same-as` compares each line that isn't blank as one value. Before, the whole block was
+  one value, so `same-as-mode` and `same-as-format` didn't work on a block of several lines. For example,
+  `same-as-mode="single"` passed with two lines, `subset` failed on a line that the target had, and `numeric` reported
+  that `1` and `2` together are not a number ([#179](https://github.com/mennanov/blockwatch/issues/179)).
+- Without `same-as-mode`, a block without `same-as-pattern` compares in `sequence` mode. So it still fails when its
+  lines differ from the target's or come in another order. A block with a pattern still compares in `set` mode.
+- A block without `same-as-pattern` now fails when its target's pattern finds a value more than once, or in another
+  order: `["1.2.3"] != ["1.2.3", "1.2.3"]`. Before, the default `set` mode ignored this. To keep the old result, add
+  `same-as-mode="set"`, or `same-as-mode="subset"` when the target may hold other values too.
+- `same-as` now fails on two empty blocks, as it does on a pattern that matches nothing. The message for both is
+  `this block or its target has no values to compare`.
+- `same-as-paths` no longer needs `same-as-pattern`. Without one, each line of the block must be a path, in sorted
+  order.
+- An attribute that changes how a validator works now stops the run on a block without the validator's main
+  attribute. Before, it did nothing there. For example, `same-as-mode="sequence"` on a target let values in another
+  order pass. The attributes are:
+  - `same-as-mode` and `same-as-format`, without `same-as` or `same-as-paths`;
+  - `same-as-pattern`, without `same-as`, `same-as-paths` or `name`, because only a block with a name can be a target;
+  - `keep-sorted-pattern` and `keep-sorted-format`, without `keep-sorted`;
+  - `line-count-pattern`, without `line-count`;
+  - `check-ai-pattern`, without `check-ai`;
+  - `check-lua-pattern` and `check-lua-timeout`, without `check-lua`.
+
+### Fixed
+
+- An empty alternative in braces now matches, so `{,sub/}a.yml` matches both `a.yml` and `sub/a.yml`. Before, it
+  matched only `sub/a.yml`, with no error. This was true of every glob: a `[[block]]` target, `same-as-paths`, the
+  `ignore` setting and `--ignore`, and a path argument ([#177](https://github.com/mennanov/blockwatch/issues/177)).
+
 ## [0.15.0] - 2026-10-21
 
 ### Changed

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/Cargo.lock

@@ -274,7 +274,7 @@ checksum = "3ded4057c258ba199e2d26386d3af3780957ecaee6c4ef4041c6b4b8b97c0b06"
 
 [[package]]
 name = "blockwatch"
-version = "0.15.0"
+version = "0.16.1"
 dependencies = [
  "anyhow",
  "assert-json-diff",

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "blockwatch"
-version = "0.15.0"
+version = "0.16.1"
 edition = "2024"
 repository = "https://github.com/mennanov/blockwatch"
 description = "Language agnostic linter that keeps your code and documentation in sync and valid"

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: blockwatch-cli
-Version: 0.15.0
+Version: 0.16.1
 Summary: Language agnostic linter that keeps your code and documentation in sync and valid
 Keywords: linter,sync,drift,comments,agents
 Home-Page: https://github.com/mennanov/blockwatch

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/README.md

@@ -88,9 +88,10 @@ Two validators work across files:
 - `affects` fails when a diff touches a block without also changing what it points to.
 - `same-as` fails when a block and its target hold different values. It needs no diff.
 
-Both can point to a block, a whole file, a specific value in a file like `package.json#/version`, or a section of a
-Markdown file (see [Symbols](docs/symbols.md)). The other validators check a single block on their own: the things
-you'd otherwise have to nitpick in code review.
+Both can point to a block, a whole file, a specific value in a file like `package.json#/version`, a section of a
+Markdown file, or a constant in a Go, C, C++, Python, Rust, TypeScript or JavaScript file (see
+[Symbols](docs/symbols.md)). The other validators check a single block on their own: the things you'd otherwise have to
+nitpick in code review.
 
 <!-- <block name="available-validators"
      same-as="src/validators/mod.rs:validator-registry, docs/validators/README.md:validators-index"
@@ -218,7 +219,7 @@ exclusions, and custom extension mappings.
 
 ```yaml
 - repo: https://github.com/mennanov/blockwatch
-  rev: v0.15.0  # Use latest release
+  rev: v0.16.1  # Use latest release
   hooks:
     - id: blockwatch
 ```

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/blockwatch.toml

@@ -50,4 +50,4 @@ same-as-pattern = '^\|\s*`(?P<value>[a-z-]+)`'
 [[block]]
 target = 'src/skill.md#/blockwatch/Symbols/Files with symbols'
 name = 'extensions-with-symbols'
-same-as-pattern = '`\.?(?P<value>[A-Za-z]+)`'
+same-as-pattern = '`\.?(?P<value>[A-Za-z.]+)`'

blockwatch_cli-0.16.1/clippy.toml

@@ -0,0 +1,11 @@
+# The integration tests run inside this repository, so a run would read its blockwatch.toml, which
+# skips tests/testdata.
+disallowed-macros = [
+    { path = "assert_cmd::cargo_bin_cmd", reason = "use common::cargo_bin_cmd!, which passes an empty config" },
+]
+# globset drops an empty alternative in braces by default, so `{,sub/}a.yml` would not match
+# `a.yml`.
+disallowed-methods = [
+    { path = "globset::Glob::new", reason = "use paths_glob::glob_builder, which keeps an empty alternative" },
+    { path = "globset::GlobBuilder::new", reason = "use paths_glob::glob_builder, which keeps an empty alternative" },
+]

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/docs/ci.md

@@ -19,7 +19,7 @@ To use [pre-commit](https://pre-commit.com), add the hook to `.pre-commit-config
 
 ```yaml
 - repo: https://github.com/mennanov/blockwatch
-  rev: v0.15.0  # Use latest release
+  rev: v0.16.1  # Use latest release
   hooks:
     - id: blockwatch
 ```
@@ -59,7 +59,7 @@ The `blockwatch` hook runs before the commit message exists, so it cannot see a
 
 ```yaml
 - repo: https://github.com/mennanov/blockwatch
-  rev: v0.15.0  # Use latest release
+  rev: v0.16.1  # Use latest release
   hooks:
     - id: blockwatch-commit-msg
 ```

{blockwatch_cli-0.15.0 → blockwatch_cli-0.16.1}/docs/cli.md

@@ -557,15 +557,15 @@ Nothing else about the run changes: the same violations are found, and the exit
       "tool": {
         "driver": {
           "name": "blockwatch",
-          "version": "0.15.0",
-          "semanticVersion": "0.15.0",
+          "version": "0.16.1",
+          "semanticVersion": "0.16.1",
           "informationUri": "https://github.com/mennanov/blockwatch",
           "rules": [
             {
               "id": "keep-sorted",
               "name": "keep-sorted",
               "shortDescription": { "text": "Requires the lines of a block to stay in order." },
-              "helpUri": "https://github.com/mennanov/blockwatch/blob/v0.15.0/docs/validators/keep-sorted.md"
+              "helpUri": "https://github.com/mennanov/blockwatch/blob/v0.16.1/docs/validators/keep-sorted.md"
             }
           ]
         }
@@ -790,16 +790,16 @@ A trace stops where its validator stops, such as at the first line out of order.
 file, and `text` is that line trimmed, as the validator compares it. A key that holds what a violation reports has the
 name the violation's `data` gives it, such as `reason`.
 
-| Validator      | What it shows                                                                                                                                                                                                                                                                                                                                                                          |
-|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `same-as`      | `records`: each match of `same-as-pattern` in the block, with its `line`, the text the regex matched (`match`), and each named group after `same-as-format` (`groups`). `targets`: the `records` of each target, and the `reason` of its violation, or `null` when the two agree. `paths`: with `same-as-paths`, the `glob`, the paths it `matched`, their `records` and the `reason`. |
-| `keep-sorted`  | `lines`: each line read, with the `value` it compares, or `null` when `keep-sorted-pattern` skips the line. `format` and `order`.                                                                                                                                                                                                                                                      |
-| `keep-unique`  | `lines`, as for `keep-sorted`. A repeated value has `duplicate_of`: the line where it first appeared.                                                                                                                                                                                                                                                                                  |
-| `line-pattern` | `lines`: each line read, with the text `line-pattern` matched (`match`). A line that fails has `fails`: the check it fails. `forbidden_match` is the text `line-pattern-forbidden` found.                                                                                                                                                                                              |
-| `line-count`   | `lines`, as for `keep-sorted`. A line counts when its `value` isn't `null`. The number of lines counted (`actual`), and the rule (`op` and `expected`).                                                                                                                                                                                                                                |
-| `affects`      | Whether the diff changed the block (`block_changed`). For each target: whether the diff `changed` it, or the `reason` it doesn't resolve.                                                                                                                                                                                                                                              |
-| `check-lua`    | The `content` and the `affects` the script got, and the message it returned (`lua_error`), or `null` when it passed. `affects` is `ctx.affects` without the content of each target.                                                                                                                                                                                                    |
-| `check-ai`     | The `model`, the `prompt` sent and the `response`. Both are `null` when `check-ai-pattern` matched nothing, so no request was sent.                                                                                                                                                                                                                                                    |
+| Validator      | What it shows                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `same-as`      | `records`: each match of `same-as-pattern` in the block, or each line without a pattern, with its `line`, the text the regex matched (`match`), and each named group after `same-as-format` (`groups`). `mode`: the `same-as-mode` it compared with. `targets`: the `records` of each target, and the `reason` of its violation, or `null` when the two agree. `paths`: with `same-as-paths`, the `glob`, the paths it `matched`, their `records` and the `reason`. |
+| `keep-sorted`  | `lines`: each line read, with the `value` it compares, or `null` when `keep-sorted-pattern` skips the line. `format` and `order`.                                                                                                                                                                                                                                                                                                                                   |
+| `keep-unique`  | `lines`, as for `keep-sorted`. A repeated value has `duplicate_of`: the line where it first appeared.                                                                                                                                                                                                                                                                                                                                                               |
+| `line-pattern` | `lines`: each line read, with the text `line-pattern` matched (`match`). A line that fails has `fails`: the check it fails. `forbidden_match` is the text `line-pattern-forbidden` found.                                                                                                                                                                                                                                                                           |
+| `line-count`   | `lines`, as for `keep-sorted`. A line counts when its `value` isn't `null`. The number of lines counted (`actual`), and the rule (`op` and `expected`).                                                                                                                                                                                                                                                                                                             |
+| `affects`      | Whether the diff changed the block (`block_changed`). For each target: whether the diff `changed` it, or the `reason` it doesn't resolve.                                                                                                                                                                                                                                                                                                                           |
+| `check-lua`    | The `content` and the `affects` the script got, and the message it returned (`lua_error`), or `null` when it passed. `affects` is `ctx.affects` without the content of each target.                                                                                                                                                                                                                                                                                 |
+| `check-ai`     | The `model`, the `prompt` sent and the `response`. Both are `null` when `check-ai-pattern` matched nothing, so no request was sent.                                                                                                                                                                                                                                                                                                                                 |
 
 ## Run Reports