update dependencies

.eslintrc.json

@@ -11,6 +11,7 @@
  "i18n-text/no-en": "off",
  "eslint-comments/no-use": "off",
  "import/no-namespace": "off",
+ "import/no-named-as-default": "off",
  "no-shadow": "off",
  "no-unused-vars": "off",
  "prefer-template": "off",
@@ -60,29 +61,7 @@
  },
  "import/resolver": {
  "typescript": {
- "alwaysTryTypes": true, // always try to resolve types under `<root>@types` directory even it doesn't contain any source code, like `@types/unist`
-
- // Choose from one of the "project" configs below or omit to use <root>/tsconfig.json by default
-
- // use <root>/path/to/folder/tsconfig.json
- "project": "path/to/folder",
-
- // Multiple tsconfigs (Useful for monorepos)
-
- // use a glob pattern
- "project": "packages/*/tsconfig.json",
-
- // use an array
- "project": [
- "packages/module-a/tsconfig.json",
- "packages/module-b/tsconfig.json"
- ],
-
- // use an array of glob patterns
- "project": [
- "packages/*/tsconfig.json",
- "other-packages/*/tsconfig.json"
- ]
+ "alwaysTryTypes": true // always try to resolve types under `<root>@types` directory even it doesn't contain any source code, like `@types/unist`
  }
  }
  }

.github/workflows/check-dist.yml

@@ -24,7 +24,7 @@ jobs:
  - uses: actions/checkout@v2
 
  - name: Set Node.js 16.x
- uses: actions/setup-node@v3.5.1
+ uses: actions/setup-node@v3
  with:
  node-version: 16.x
 
@@ -46,7 +46,7 @@ jobs:
  id: diff
 
  # If index.js was different than expected, upload the expected version as an artifact
- - uses: actions/upload-artifact@v2
+ - uses: actions/upload-artifact@v3
  if: ${{ failure() && steps.diff.conclusion == 'failure' }}
  with:
  name: dist

.github/workflows/ci.yml

@@ -13,7 +13,7 @@ jobs:
  name: Build & Test
  runs-on: ubuntu-latest
  steps:
- - uses: actions/checkout@v2
+ - uses: actions/checkout@v3
  - run: node --version
  - run: npm ci
  - run: npm run build
@@ -23,7 +23,7 @@ jobs:
 
  - name: Upload test results
  if: success() || failure()
- uses: actions/upload-artifact@v2
+ uses: actions/upload-artifact@v3
  with:
  name: test-results
  path: __tests__/__results__/*.xml

.github/workflows/manual-run.yml

@@ -8,7 +8,7 @@ jobs:
  runs-on: ubuntu-latest
 
  steps:
- - uses: actions/checkout@v2
+ - uses: actions/checkout@v3
  - run: npm ci
  - run: npm run build
  - run: npm test

.github/workflows/test-report.yml

@@ -11,7 +11,7 @@ jobs:
  name: Workflow test
  runs-on: ubuntu-latest
  steps:
- - uses: actions/checkout@v2
+ - uses: actions/checkout@v3
  - uses: ./
  with:
  artifact: test-results

README.md

@@ -38,7 +38,7 @@ jobs:
  name: Build & Test
  runs-on: ubuntu-latest
  steps:
- - uses: actions/checkout@v2 # checkout the repo
+ - uses: actions/checkout@v3 # checkout the repo
  - run: npm ci # install packages
  - run: npm test # run tests (configured to use jest-junit reporter)
 
@@ -69,10 +69,10 @@ jobs:
  build-test:
  runs-on: ubuntu-latest
  steps:
- - uses: actions/checkout@v2 # checkout the repo
+ - uses: actions/checkout@v3 # checkout the repo
  - run: npm ci # install packages
  - run: npm test # run tests (configured to use jest-junit reporter)
- - uses: actions/upload-artifact@v2 # upload test results
+ - uses: actions/upload-artifact@v3 # upload test results
  if: success() || failure() # run this step even if previous step failed
  with:
  name: test-results
@@ -310,7 +310,7 @@ Unfortunately, there are some known issues and limitations caused by GitHub API:
 
 - Test report (i.e. Check Run summary) is markdown text. No custom styling or HTML is possible.
 - Maximum report size is 65535 bytes. Input parameters `list-suites` and `list-tests` will be automatically adjusted if max size is exceeded.
-- Test report can't reference any additional files (e.g. screenshots). You can use `actions/upload-artifact@v2` to upload them and inspect them manually.
+- Test report can't reference any additional files (e.g. screenshots). You can use `actions/upload-artifact@v3` to upload them and inspect them manually.
 - Check Runs are created for specific commit SHA. It's not possible to specify under which workflow test report should belong if more
  workflows are running for the same SHA. Thanks to this GitHub "feature" it's possible your test report will appear in an unexpected place in GitHub UI.
  For more information, see [#67](https://github.com/dorny/test-reporter/issues/67).