From 8f36057ad3909fbb257ee868e2b4d179cfc32eaa Mon Sep 17 00:00:00 2001 From: yukimemi Date: Fri, 4 Sep 2026 08:38:32 +0900 Subject: [PATCH] fix(ci): bump the editorconfig-checker action past the v4 rename The `editorconfig` job has been failing on every consumer repo with Error: The binary 'ec-linux-amd64*' not found not on a rule violation. `editorconfig-checker` v4.0.0 renamed its release assets from `ec--` to `editorconfig-checker--`, and `action-editorconfig-checker@v2` still looks for the old name, so it cannot fetch the binary it is supposed to run. `v3.0.0` of the action is exactly that fix - "support editorconfig-checker binary name for v4 with legacy `ec` fallback" - and it shipped today. Found on yukimemi/magi, where the job had gone red on every commit since the sweep switched it on. Worth pinning rather than floating on `v3`: this is the second time the pair has drifted, and a tag keeps Renovate in charge of when it moves. --- vars.rust.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vars.rust.toml b/vars.rust.toml index 9d1f6c3..f02fdbd 100644 --- a/vars.rust.toml +++ b/vars.rust.toml @@ -22,4 +22,4 @@ swatinem_rust_cache = "v2" # renovate: datasource=github-tags depName=editorconfig-checker/action-editorconfig-checker -editorconfig_checker = "v2" +editorconfig_checker = "v3.0.0"