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

{blockwatch_cli-0.14.2 → blockwatch_cli-0.15.0}/.pre-commit-config.yaml

@@ -43,6 +43,14 @@ repos:
         types: [ rust ]
         stages: [ pre-commit ]
         pass_filenames: false
+      - id: cargo-test
+        name: cargo test
+        description: Run the unit, integration and doc tests.
+        entry: cargo test --quiet
+        language: system
+        types: [ rust ]
+        stages: [ pre-commit ]
+        pass_filenames: false
 
   # Rules and the set of files linted live in `.markdownlint-cli2.yaml`, which the tool picks up
   # from the repository root. The hook passes only the staged Markdown files, so a commit is judged

{blockwatch_cli-0.14.2 → blockwatch_cli-0.15.0}/AGENTS.md

@@ -65,9 +65,9 @@ For example:
 - *Always* handle the variants of an enum with an exhaustive `match`. A `let ... else`, or an `if` that handles one
   variant and sends the rest to a single branch, quietly gives any new variant whatever that branch does. With a
   `match`, the compiler makes you decide what to do with each new variant. One exception: a `match` on another
-  crate's enum can end with `_` when it only asks whether a value is one variant, and no new variant could be that
-  one. For example, every Markdown heading is `mdast::Node::Heading`, so the other node types can go to `_ => None`.
-  Say why in a comment next to the `_`.
+  crate's enum can end with `_` when it only picks out one or a few variants, and no new variant could be one of
+  them. For example, every Markdown heading is `mdast::Node::Heading`, so the other node types can go to
+  `_ => None`. Say why in a comment next to the `_`.
 - *Always* give an item the narrowest visibility that compiles: private, then `pub(super)`, then `pub(crate)`.
   blockwatch is a program, not a library. Only `run` and `count_rust_blocks` in `lib.rs` are `pub`, for `main.rs` and
   the fuzz target. The `unreachable_pub` lint makes `cargo clippy -- -D warnings` fail on any other `pub`.
@@ -173,8 +173,9 @@ The whole pipeline is in `src/cli.rs`. `src/main.rs` only calls `blockwatch::run
    from the command line select, and that don't match the settings' ignore globs. `PathArguments::resolve` turns an
    existing file or directory into a glob first, so `src` selects `src/**`. Pick each file's language by its
    extension, using the settings' extension mappings too.
-6. For each file, the matching `language_parsers::<lang>` (a tree-sitter grammar) finds the comments. `tag_parser` and
-   `block_parser` turn the comment text into `Block` values, with their attributes and their byte and line ranges.
+6. For each file, the matching `language_parsers::<lang>` (usually a tree-sitter grammar) finds the comments.
+   `tag_parser` and `block_parser` turn the comment text into `Block` values, with their attributes and their byte and
+   line ranges.
    `VirtualBlock::resolve` finds each virtual block in the file, by its `Locator`, and adds it as a `Block` too. A file
    without a grammar is read as plain text: it has no tags, only its virtual blocks. A target that does not resolve
    stops the run. `--only-changed` also parses the file of a virtual block whose entry the diff
@@ -224,7 +225,8 @@ The main modules:
 - `src/repo_path.rs` — `RepoPath`, the one way to write a path relative to the repository root. A diff header
   (`b/src/main.rs`), a path found in the walk and a `file:name` attribute all become a `RepoPath`. So the same file is
   always the same map key.
-- `src/language_parsers/` — one tree-sitter grammar for each language. Each language has a `parser()` that returns a
+- `src/language_parsers/` — one parser for each language, most of them a tree-sitter grammar. Markdown and MDX use
+  the `markdown` crate, and Lean has its own scanner. Each language has a `parser()` that returns a
   `LanguageParser`, which knows which syntax nodes are comments. `src/block_parser.rs` turns those comments into
   blocks. `language_parsers()` in `language_parsers/mod.rs` returns `LanguageParsers`: the parser of each extension.
   Its `parser_for` picks the parser of a file, using the settings' extension mappings too. **To add a language, add a
@@ -238,8 +240,7 @@ The main modules:
     syntax tree is nested.
   - YAML walks its syntax tree itself. An alias has a position in a sequence but can't be addressed, and a query can't
     express that.
-  - Markdown finds its sections with the `markdown` crate. The `section` nodes of `tree-sitter-md` don't end at a
-    heading underlined with `---`.
+  - Markdown finds its sections with the `markdown` crate, the same parser that finds its comments.
 
   Each language's tests list every symbol it finds. When you give a language symbols, also document its paths in
   `docs/symbols.md` and in the "Symbols" section of the skill, `src/skill.md`. A test in `language_parsers/mod.rs` and the

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

@@ -12,6 +12,25 @@ Releases up to and including v0.3.11 predate this file. Their notes live on the
 
 ## [Unreleased] - ReleaseDate
 
+## [0.15.0] - 2026-10-21
+
+### Changed
+
+- In Markdown, a `<!--` is a comment only where HTML is kept as it is: in an HTML block or in raw HTML in a line of
+  text. These were read as comments before and are not now:
+  - the alt text of an image: `![Logo <!-- x -->](logo.png)`;
+  - the title of a link: `[Docs](docs.md "<!-- x -->")`;
+  - an escaped `<`: `\<!-- x -->`.
+
+  In a line of text, `<!-->` is now a whole comment, so a tag after it on that line is not read.
+
+### Fixed
+
+- In Markdown, blockwatch skipped every tag after a fenced code block that holds a line like `` ``` `` indented by 4
+  spaces or a tab, or `` echo x``` ``. Such a line closed the code block too early, so the rest of the file became
+  code. The run gave no error. Now such a line stays in the code block, as CommonMark says
+  ([#176](https://github.com/mennanov/blockwatch/issues/176)).
+
 ## [0.14.2] - 2026-10-21
 
 ### Added

{blockwatch_cli-0.14.2 → blockwatch_cli-0.15.0}/CLAUDE.md

@@ -65,9 +65,9 @@ For example:
 - *Always* handle the variants of an enum with an exhaustive `match`. A `let ... else`, or an `if` that handles one
   variant and sends the rest to a single branch, quietly gives any new variant whatever that branch does. With a
   `match`, the compiler makes you decide what to do with each new variant. One exception: a `match` on another
-  crate's enum can end with `_` when it only asks whether a value is one variant, and no new variant could be that
-  one. For example, every Markdown heading is `mdast::Node::Heading`, so the other node types can go to `_ => None`.
-  Say why in a comment next to the `_`.
+  crate's enum can end with `_` when it only picks out one or a few variants, and no new variant could be one of
+  them. For example, every Markdown heading is `mdast::Node::Heading`, so the other node types can go to
+  `_ => None`. Say why in a comment next to the `_`.
 - *Always* give an item the narrowest visibility that compiles: private, then `pub(super)`, then `pub(crate)`.
   blockwatch is a program, not a library. Only `run` and `count_rust_blocks` in `lib.rs` are `pub`, for `main.rs` and
   the fuzz target. The `unreachable_pub` lint makes `cargo clippy -- -D warnings` fail on any other `pub`.
@@ -173,8 +173,9 @@ The whole pipeline is in `src/cli.rs`. `src/main.rs` only calls `blockwatch::run
    from the command line select, and that don't match the settings' ignore globs. `PathArguments::resolve` turns an
    existing file or directory into a glob first, so `src` selects `src/**`. Pick each file's language by its
    extension, using the settings' extension mappings too.
-6. For each file, the matching `language_parsers::<lang>` (a tree-sitter grammar) finds the comments. `tag_parser` and
-   `block_parser` turn the comment text into `Block` values, with their attributes and their byte and line ranges.
+6. For each file, the matching `language_parsers::<lang>` (usually a tree-sitter grammar) finds the comments.
+   `tag_parser` and `block_parser` turn the comment text into `Block` values, with their attributes and their byte and
+   line ranges.
    `VirtualBlock::resolve` finds each virtual block in the file, by its `Locator`, and adds it as a `Block` too. A file
    without a grammar is read as plain text: it has no tags, only its virtual blocks. A target that does not resolve
    stops the run. `--only-changed` also parses the file of a virtual block whose entry the diff
@@ -224,7 +225,8 @@ The main modules:
 - `src/repo_path.rs` — `RepoPath`, the one way to write a path relative to the repository root. A diff header
   (`b/src/main.rs`), a path found in the walk and a `file:name` attribute all become a `RepoPath`. So the same file is
   always the same map key.
-- `src/language_parsers/` — one tree-sitter grammar for each language. Each language has a `parser()` that returns a
+- `src/language_parsers/` — one parser for each language, most of them a tree-sitter grammar. Markdown and MDX use
+  the `markdown` crate, and Lean has its own scanner. Each language has a `parser()` that returns a
   `LanguageParser`, which knows which syntax nodes are comments. `src/block_parser.rs` turns those comments into
   blocks. `language_parsers()` in `language_parsers/mod.rs` returns `LanguageParsers`: the parser of each extension.
   Its `parser_for` picks the parser of a file, using the settings' extension mappings too. **To add a language, add a
@@ -238,8 +240,7 @@ The main modules:
     syntax tree is nested.
   - YAML walks its syntax tree itself. An alias has a position in a sequence but can't be addressed, and a query can't
     express that.
-  - Markdown finds its sections with the `markdown` crate. The `section` nodes of `tree-sitter-md` don't end at a
-    heading underlined with `---`.
+  - Markdown finds its sections with the `markdown` crate, the same parser that finds its comments.
 
   Each language's tests list every symbol it finds. When you give a language symbols, also document its paths in
   `docs/symbols.md` and in the "Symbols" section of the skill, `src/skill.md`. A test in `language_parsers/mod.rs` and the

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

@@ -274,7 +274,7 @@ checksum = "3ded4057c258ba199e2d26386d3af3780957ecaee6c4ef4041c6b4b8b97c0b06"
 
 [[package]]
 name = "blockwatch"
-version = "0.14.2"
+version = "0.15.0"
 dependencies = [
  "anyhow",
  "assert-json-diff",
@@ -327,7 +327,6 @@ dependencies = [
  "tree-sitter-kotlin-ng",
  "tree-sitter-lua",
  "tree-sitter-make",
- "tree-sitter-md",
  "tree-sitter-nix",
  "tree-sitter-ocaml",
  "tree-sitter-php",
@@ -2637,16 +2636,6 @@ dependencies = [
  "tree-sitter-language",
 ]
 
-[[package]]
-name = "tree-sitter-md"
-version = "0.5.3"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "2efd398be546456c814598ee56c0f51769a77241511b4a58077815d120afa882"
-dependencies = [
- "cc",
- "tree-sitter-language",
-]
-
 [[package]]
 name = "tree-sitter-nix"
 version = "0.3.0"

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

@@ -1,6 +1,6 @@
 [package]
 name = "blockwatch"
-version = "0.14.2"
+version = "0.15.0"
 edition = "2024"
 repository = "https://github.com/mennanov/blockwatch"
 description = "Language agnostic linter that keeps your code and documentation in sync and valid"
@@ -62,7 +62,6 @@ tree-sitter-json = "0.24.8"
 tree-sitter-kotlin-ng = "1.1"
 tree-sitter-lua = "0.5"
 tree-sitter-make = "1.1"
-tree-sitter-md = "0.5"
 tree-sitter-nix = "0.3.0"
 tree-sitter-ocaml = "0.26"
 tree-sitter-php = "0.25"

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: blockwatch-cli
-Version: 0.14.2
+Version: 0.15.0
 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.14.2 → blockwatch_cli-0.15.0}/README.md

@@ -218,7 +218,7 @@ exclusions, and custom extension mappings.
 
 ```yaml
 - repo: https://github.com/mennanov/blockwatch
-  rev: v0.14.2  # Use latest release
+  rev: v0.15.0  # Use latest release
   hooks:
     - id: blockwatch
 ```

{blockwatch_cli-0.14.2 → blockwatch_cli-0.15.0}/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.14.2  # Use latest release
+  rev: v0.15.0  # 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.14.2  # Use latest release
+  rev: v0.15.0  # Use latest release
   hooks:
     - id: blockwatch-commit-msg
 ```

{blockwatch_cli-0.14.2 → blockwatch_cli-0.15.0}/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.14.2",
-          "semanticVersion": "0.14.2",
+          "version": "0.15.0",
+          "semanticVersion": "0.15.0",
           "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.14.2/docs/validators/keep-sorted.md"
+              "helpUri": "https://github.com/mennanov/blockwatch/blob/v0.15.0/docs/validators/keep-sorted.md"
             }
           ]
         }

{blockwatch_cli-0.14.2 → blockwatch_cli-0.15.0}/setup.py

@@ -6,7 +6,7 @@ setup(
     name='blockwatch-pre-commit-placeholder',
     version='0.0.0',
     # <block name="blockwatch-cli-version" same-as-pattern="blockwatch-cli==(?P<value>\d+\.\d+\.\d+)">
-    install_requires=['blockwatch-cli==0.14.2'],
+    install_requires=['blockwatch-cli==0.15.0'],
     # </block>
     # Without it, setuptools takes the directories under src/ for Python packages.
     packages=[],