#47303: ci: add a problem matcher for ESLint output
Merged
Description of Change
Will catch errors like the lint failure currently on main. This is taken verbatim from https://github.com/actions/setup-node/blob/49933ea5288caeca8642d1e84afbd3f7d6820020/.github/eslint-stylish.json, which is automatically injected for jobs using actions/setup-node, but we usually use the Node.js version on our runners, and specifically our lint job does not use actions/setup-node.
Checklist
- PR description included and stakeholders cc'd
Release Notes
Notes: none
Backports
34-x-y
MergedPR Number
#47307Merged At
Jun 2, 2025, 12:48:23 PM
Released In
v34.5.8Release Date
Jun 4, 2025, 3:20:19 AM
35-x-y
MergedPR Number
#47306Merged At
May 30, 2025, 4:02:04 AM
Released In
v35.5.1Release Date
Jun 3, 2025, 7:23:30 PM
36-x-y
MergedPR Number
#47308Merged At
May 30, 2025, 4:03:04 AM
Released In
v36.4.0Release Date
Jun 3, 2025, 6:30:14 PM
37-x-y
MergedPR Number
#47305Merged At
May 30, 2025, 4:00:37 AM
Released In
v37.0.0-beta.2Release Date
Jun 2, 2025, 8:31:18 AM
Semver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron