build(deps): bump @sshadows/tree-sitter-al from 3.0.1 to 4.0.1

[dependabot]

Bumps @sshadows/tree-sitter-al from 3.0.1 to 4.0.1.

Release notes

Sourced from @​sshadows/tree-sitter-al's releases.

v4.0.1

tree-sitter-al v4.0.1

File	Platform	Use case
tree-sitter-al.wasm	All	web-tree-sitter
tree-sitter-al.so	Linux x86_64	ast-grep, native bindings
tree-sitter-al.dll	Windows x86_64	ast-grep, native bindings
tree-sitter-al.dylib	macOS ARM64	ast-grep, native bindings

v4.0.0

tree-sitter-al v4.0.0

File	Platform	Use case
tree-sitter-al.wasm	All	web-tree-sitter
tree-sitter-al.so	Linux x86_64	ast-grep, native bindings
tree-sitter-al.dll	Windows x86_64	ast-grep, native bindings
tree-sitter-al.dylib	macOS ARM64	ast-grep, native bindings

v3.3.1

tree-sitter-al v3.3.1

File	Platform	Use case
tree-sitter-al.wasm	All	web-tree-sitter
tree-sitter-al.so	Linux x86_64	ast-grep, native bindings
tree-sitter-al.dll	Windows x86_64	ast-grep, native bindings
tree-sitter-al.dylib	macOS ARM64	ast-grep, native bindings

v3.3.0

tree-sitter-al v3.3.0

File	Platform	Use case
tree-sitter-al.wasm	All	web-tree-sitter
tree-sitter-al.so	Linux x86_64	ast-grep, native bindings
tree-sitter-al.dll	Windows x86_64	ast-grep, native bindings
tree-sitter-al.dylib	macOS ARM64	ast-grep, native bindings

Changelog

Sourced from @​sshadows/tree-sitter-al's changelog.

[4.0.1] — 2026-08-12

Three defects, all found the same way: by someone outside this repository using the published artifacts. Each lived in a configuration the project never exercises itself — a C compiler invoked with default flags, a keyword used as a variable name, a wasm loaded instead of the native library — so every gate here stayed green over all three. The release therefore ships a gate per defect, not just the fixes.

Validated over 36,852 production AL files across two independent codebases (15,358 + 21,494), 0 errors. 1,617 tests pass.

Fixed

• src/scanner.c did not compile under MSVC's default flags. The _Static_assert that pins ScannerDepth to an unsigned 32-bit type was guarded by (defined(_MSC_VER) && _MSC_VER >= 1928) || (__STDC_VERSION__ >= 201112L). The first arm is wrong: MSVC's C compiler rejects _Static_assert at every version unless /std:c11 or /std:c17 is passed, and those are exactly the modes in which it defines __STDC_VERSION__. So the _MSC_VER arm enabled the assert precisely where it does not compile, and any consumer building the file with default flags got C2143: syntax error: missing ')' before '('. Measured on 19.44.35228. The guard is now __STDC_VERSION__ alone; default-flags MSVC takes the negative-array fallback, which compiles and still fails the build if the counter is narrowed.

  Every first-party build passes c11 already — Makefile (-std=c11), binding.gyp (/std:c11), setup.py (both spellings), bindings/rust/build.rs (cc.std("c11")), bindings/go/binding.go (cgo CFLAGS) — which is why the whole CI matrix stayed green over a file that did not build. New CI job scanner-default-flags compiles src/scanner.c on windows-latest with no /std flag. It also narrows ScannerDepth to uint8_t and requires the build to fail both ways, because "it compiles clean" passes just as well with the guard deleted.

• 14 section keywords are legal AL variable names and would not parse. Filter: Codeunit "Some Thing"; failed, while Filters, MyFilter, Assert and Count were fine. Sweeping all 151 named keyword rules as variable names found 23 failures; alc 18.0.37.11445 accepts 14 of them, now added to keyword_as_identifier: filter, column, dataitem, elements, fields, keys, labels, layout, modify, rendering, requestpage, schema, views, analysisviews. The other nine are rejected by alc too and stay rejected here. Present in 2.5.1, so it predates 4.0.0.

• The shipped tree-sitter-al.wasm was a release behind. It was last built for v4.0.0; the keyword fix above landed after it. build-wasm.yml's release job does not build the wasm — it runs cp tree-sitter-al.wasm artifacts/ — so the file in git is the artifact, and npm ships it too (files includes *.wasm). Verified by loading both in web-tree-sitter 0.26.12 rather than inferred from dates: on `codeunit 80228 "T" { var Filter: Codeunit "Some

... (truncated)

Commits

• 58c236f chore: regenerate parser.c and rebuild tree-sitter-al.wasm for v4.0.1
• 2690d04 chore: bump version to 4.0.1
• a2d93b1 docs(release): the wasm step's three gaps -- trigger, channels, verification
• 05e6288 fix(ci): the wasm stamp was platform-dependent, so the gate failed on Linux
• bed960a fix(ci): the wasm gate's first run failed at exit 126, having never run
• b2dfaaa fix(wasm): the shipped wasm was a release behind, and nothing could see it
• 39d2632 docs(deferred): the gate self-test's 5 failures are 2 clusters, and 2 are con...
• 7b3da17 docs(spec): track the expose-keywords design, the only untracked spec
• 94b7cbc docs: track the deferred-work list and three notes that lived only on one disk
• 3bac021 fix(scanner): _MSC_VER is not a proxy for _Static_assert; MSVC default builds...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​sshadows/tree-sitter-al since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)