SRE-927: Ignore the concurrency.queue syntax gap

[TimDiekmann]

Purpose

actionlint 1.7.12 does not know the concurrency.queue key (rhysd/actionlint#654), which hashintel/hash uses in its deploy workflow. Same category as the $/ ignores from #100: a real GitHub feature the linter lags behind on.

Related links

• SRE-927 (internal)
• SRE-941 (internal)

What does this change?

• Third -ignore on the actionlint step for the concurrency.queue syntax-check message, tracked for removal in SRE-941 alongside the $/ ignores

The intermediate commit gating shellcheck at error level is reverted — findings in the consumer repos get fixed instead (SRE-927 fleet PRs).

[cursor]

PR Summary

Low Risk
CI lint configuration only; no runtime or security impact.

Overview
Preflight actionlint now ignores the unexpected key "queue" for "concurrency" section diagnostic so workflows using GitHub’s valid concurrency.queue setting (e.g. in consumer repos) don’t fail CI while actionlint lags behind (rhysd/actionlint#654).

The existing SRE-941 TODO is extended to drop this ignore alongside the $/ rules once upstream supports both syntaxes.

^{Reviewed by Cursor Bugbot for commit d7a1c9b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Copilot]

Pull request overview

Updates the reusable actionlint preflight workflow to suppress a known false-positive triggered by GitHub Actions’ concurrency.queue syntax, which actionlint v1.7.12 does not yet recognize (tracked for later removal alongside existing $/ ignores).

Changes:

• Add a third -ignore pattern to filter the concurrency.queue “unexpected key" lint message.
• Expand the TODO comment to track both upstream actionlint gaps ($/ and concurrency.queue) under SRE-941.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.