[glasstiger]

Patch bump 0.1.19 to 0.1.20.

Covers the one change merged since 0.1.19: #37, which registers the Enterprise ACL inspection functions active_permissions() and active_grants() as table-valued functions.

Changes

• package.json: version 0.1.19 to 0.1.20.
• CHANGELOG.md: new ## 0.1.20 - 2026.10.21 section under ### Added, using the same heading, date, and PR-link format as earlier entries.

Verification

• yarn install --immutable: passes; yarn.lock is unchanged (the workspace is pinned as 0.0.0-use.local).
• yarn typecheck, yarn lint: clean.
• yarn build: ESM + CJS build clean; active_permissions / active_grants are present in dist/index.* and dist/grammar/index.*.
• yarn test: 15106 passed (20 files).
• npm pack --dry-run: @questdb/sql-parser@0.1.20, 40 files.
• Ran release.yml's changelog-extraction script locally against VERSION=0.1.20. It picks up the new section correctly.
• 0.1.20 is not yet on npm, so release.yml will publish it once this is merged.

Note: GitHub Release step is expected to fail

When this merges, release.yml should publish to npm, but its final Create GitHub Release step will most likely fail the same way it did for 0.1.18 and 0.1.19 (e.g. run 36009359331):

Cannot create ref due to creations being restricted. / Published releases must have a valid tag

The org-level restrict-tag-pushing ruleset blocks tag creation, and nothing is listed as a bypass actor. That is why the last GitHub release and tag is v0.1.11, even though npm has every version through 0.1.19. Fixing it needs an org admin to either add a bypass for the release workflow or change how the release step creates tags. That is out of scope for this PR.