chore(deps): update ferrlabs/.github digest to 539e9ac

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
FerrLabs/.github (changelog)	workflow	digest	15286b3 → 539e9ac

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ferrfleet]

Digest bump for FerrLabs/.github (15286b3 → fba6f4b), pinning six reusable workflow calls in docker.yml, release.yml, renovate-rebase.yml, security-scan.yml, sonarqube.yml.

Only one commit sits between the two digests (#334, "let a caller disambiguate the concurrency group per call"). It adds a new concurrency-key input to reusable-ci-node.yml and reusable-sonarqube-scan.yml, folded into the workflow-level concurrency.group string. It's optional with default: '', and LFSX's sonarqube.yml doesn't set it, so the group key is unchanged for this repo — no behavior change here. LFSX doesn't call reusable-ci-node.yml at all.

CI checks visible so far are green or still running, nothing failed.

Uneventful bump, safe to merge.

[github-actions]

SonarQube — aucune nouvelle issue

_{Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail}

[ferrfleet]

Follow-up: since my last review the PR advanced past fba6f4b to a new digest (539e9ac). The only additional upstream commit is FerrLabs/.github#331, which bumps the FerrFlow action used inside reusable-ferrflow-release.yml from v7.11.1 to v7.20.1.

Checked all 30 intervening FerrFlow releases (v7.11.2 → v7.20.1): all additive features (buildMetadata, new package-manager formats, PyPI trusted publishing, doc packaging) or bug fixes to monorepo/cascade/changelog logic, none marked breaking. The one entry that touches the area LFSX actually uses — v7.13.2 "postBump runs after changelog generation, not before" — is a schema/doc description fix only; the runtime order was already correct in v7.11.1, so LFSX's postBump: "cargo update -p lfsx-server -p lfsx" hook (.ferrflow) is unaffected.

CI is now green (SonarQube finished successfully; everything else success/skipped as expected). Uneventful, safe to merge.