release

Release tree-sitter-al

Execute the full release process for tree-sitter-al. This publishes to GitHub Releases, npm, PyPI, and crates.io.

All three registries authenticate with OIDC trusted publishing. There are no publish tokens stored in the repository.

Pre-flight Checks

Before starting, verify:

1. All tests pass: tree-sitter test

2. Production validation: ./parse-al-parallel.sh ./BC.History/ . (0 errors)

3. No unexpected ERROR/MISSING nodes in any test — this must print nothing:

   grep -rn "(ERROR\b\|(MISSING\b" test/corpus/ --include="*.txt" \
     | grep -v "ERROR(" \
     | grep -vE "(^|/)(option_members_tabledata_keyword_test|pragma_whitespace_tolerance_test|preproc_if_elif_whitespace_tolerance_test|preproc_region_whitespace_audit_test|scanner_var_attribute_token_span_test|directive_word_boundary_test|scanner_unicode_identifier_negative_test|range_not_an_expression_negative_test|preproc_split_operator_negative_test|interface_access_negative_test|missing_separator_negative_test)\.txt:"
   

   The (^|/)…\.txt: anchoring is load-bearing. grep -rn emits path:lineno:content, so an unanchored name matches anywhere in the line — including the matched source text — and would silently exempt any future fixture whose content happens to mention one of these names. Anchored, the name must be the file's own basename, which is exactly the comparison validate-grammar.sh makes.

   Both alternatives need the opening paren. This search previously read MISSING\b without it, while ERROR required (ERROR\b. Expected trees write these as (MISSING xyz) and (ERROR), so the bare form matched the word anywhere on a line — a fixture title or a prose comment containing "MISSING" failed the release. validate-grammar.sh Step 3 anchors its equivalent search to line starts and was never affected, so the two gates disagreed on what counts as a hit. Found by writing a fixture titled with the bare word.