Skip to content

fix(ci): bump editorconfig-checker action to v3.0.0 - #7

Closed
patextreme wants to merge 1 commit into
mainfrom
fix/editorconfig-checker-v3
Closed

patextreme wants to merge 1 commit into
mainfrom
fix/editorconfig-checker-v3

Conversation

@patextreme

Copy link
Copy Markdown
Contributor

Problem

editorconfig-checker published v4.0.0 on 2026-09-03, which renamed release assets from ec-linux-amd64.tar.gz to editorconfig-checker-linux-amd64.tar.gz.

The pinned action (action-editorconfig-checker@d2ed4fd, v2) downloads the latest release and looks for ec-linux-amd64* — which no longer exists. Every CI run since the release fails with:

Error: The binary 'ec-linux-amd64*' not found

This breaks the File Hygiene (editorconfig) check across all repos consuming lint-files.yml (e.g. cloud-agent PR #1876, hyperledger-identus PR #200).

Fix

Bump the action to v3.0.0 (51f63319f592f97930c73d9c46184d20bd206393), which supports the renamed assets while keeping the legacy ec-* fallback (editorconfig-checker/action-editorconfig-checker#278).

editorconfig-checker v4.0.0 renamed release assets
(ec-linux-amd64.tar.gz -> editorconfig-checker-linux-amd64.tar.gz), so the
pinned v2 action can no longer find the binary when fetching the latest
release: 'The binary ec-linux-amd64* not found'.

Action v3.0.0 supports both the renamed and legacy asset names.

Signed-off-by: Pat Losoponkul <patextreme@hotmail.com>
@patextreme
patextreme requested a review from a team as a code owner September 4, 2026 04:26
@sonarqubecloud

sonarqubecloud Bot commented Sep 4, 2026

Copy link
Copy Markdown

@patextreme patextreme closed this Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant