Releases: planningcenter/balto-eslint
Releases · planningcenter/balto-eslint
v1.0.1 - fix extension filtering
v1.0.0 - Major rewrite
Breaking changes
- Inputs and outputs now use kebab-case
neutral
conclusions are currently unsupported (still waiting on Github). Useconclusion-level
input to specifysuccess
(the default) orfailure
- We no longer install dependencies. Using balto-utils for a speedy, cached install is recommended
- Annotations have their source labeled by the job name that uses this action. We recommend naming the job
balto-eslint
.
Other changes
- Check runs have been replaced by workflow output commands, removing the need for permission tweaks and special tokens. This fixes the misattributed check run bug.
- We have official support for eslint v9!
- Overall simpler and shorter code base, optimizing for long-term stability
Internal changes
- Fully rewritten in TypeScript
- Start of automated tests for eslint v6-v9
- Using devbox to maintain a consistent dev environment
More details available in this PR: #34
Full Changelog: v0.9.0...v1.0.0
v0.9.0 - node20
v0.8.1 - Fix node12 deprecation warning
What's Changed
- docs: New version process updates by @sheck in #28
- chore: Resolve deprecation warning by upgrading node12 -> node16 by @sheck in #29
Full Changelog: v0...v0.8.1
v0.8 - output method deprecation fix
What's Changed
- Add CODEOWNERS by @breannedurenjohnson in #21
- NCC: Explicitly allow all branches by @sheck in #23
- 🐛🔧 bugfix: Add missing
semver
package by @alexandervalencia in #22 - Fix NCC workflow by @sheck in #24
- fix: Update deprecated output method by @sheck in #25
New Contributors
- @breannedurenjohnson made their first contribution in #21
Full Changelog: v0.7...v0.8
v0.7 - dependencyInstallMode
v0.6
- Feature: Add support for ESLint version 7 and up
v0.5
- Feature: Allow specifying lowest failure level with
failureLevel
- Fix: Find peer dependencies that begin with
@
- Fix: Include empty annotations array on error
Install prettier if present
Trying to track down why some project have different levels/amounts of errors reported in development vs balto. #4 eliminated some errors on an example branch.