ci: exclude parser-stack bumps from Dependabot auto-merge

[dpezto]

The tree-sitter CLI regenerates parser.c and tree-sitter-language is linked into every binding, so both change parse behavior — and no CI job here exercises the committed parser against a freshly generated one.

       - name: Enable auto-merge for patch/minor
-        if: steps.meta.outputs.update-type == 'version-update:semver-patch' || steps.meta.outputs.update-type == 'version-update:semver-minor'
+        if: >-
+          (steps.meta.outputs.update-type == 'version-update:semver-patch'
+          || steps.meta.outputs.update-type == 'version-update:semver-minor')
+          && !contains(steps.meta.outputs.dependency-names, 'tree-sitter')

Excluded by dependency name rather than by semver range, because these are 0.x packages where a minor bump is a breaking change in practice.

dependabot.yml already ignores tree-sitter-cli minors, with the reasoning that a bad 0.x bump would auto-merge silently and only surface at the next local tree-sitter generate. That reasoning applies equally to its patches and to tree-sitter-language, so this extends the same hold to both, in the place that governs merging rather than the place that governs opening.

Holding such a bump by intention alone does not work: a Dependabot PR blocked only by a merge conflict auto-merges the moment that conflict clears. The companion change in the LSP repository has the same shape, prompted by a runtime bump there that merged itself three minutes after an unrelated PR unblocked it.

Auto-merge remains enabled for everything else, including CI actions and dev tooling.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!