Releases: editorconfig-checker/action-editorconfig-checker
v2
v2.0.0
What's Changed
Breaking
Behavior change in #10
Prior to 2.0.0 the purpose of the action was to run editorconfig-checker on the files in the workspace. The purpose of the action is now solely to make editorconfig-checker available in the runner machine for use by subsequent steps in the job.
Migration Guide
A new step that invokes editorconfig-checker must be added to the workflow.
Before:
- name: Check EditorConfig compliance
uses: editorconfig-checker/action-editorconfig-checker@v1After:
- name: Install editorconfig-checker
uses: editorconfig-checker/action-editorconfig-checker@v2
- name: Check EditorConfig compliance
run: editorconfig-checkerRemoval of output output in #10
Prior to 2.0.0 the action provided an output named output that contained the output from running editorconfig-checker on the files in the workspace. This output could be referenced by the action user in subsequent steps/jobs of their workflow.
Due to the change in the action's behavior, the output is no longer provided. If needed, you can capture and use the output in the shell code of the step in the workflow that invokes editorconfig-checker.
Enhancement
- Add optional
github-tokeninput in #10 - Add optional
versioninput in #10 - refactor by @septs in #10
- Bump @types/node from 17.0.21 to 20.6.4 by @dependabot in #14
- Bump @vercel/ncc from 0.33.3 to 0.38.0 by @dependabot in #15
- Bump @actions/github from 5.0.0 to 5.1.1 by @dependabot in #16
- Bump typescript from 4.5.5 to 5.2.2 by @dependabot in #17
- Bump @actions/tool-cache from 1.7.1 to 2.0.1 by @dependabot in #18
- chore: update actions core by @mstruebing in #19
New Contributors
- @septs made their first contribution in #10
- @dependabot made their first contribution in #14
Full Changelog: v1...v2.0.0
Contributors
Assets 2
v1.0.0
release v1.0.0
v1
Release v1.0.0
0.2: Merge pull request #2 from tomtomsen/publish-action
Use unique action name