-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump eslint from 8.57.0 to 9.9.0 #4
Conversation
Dependabot will periodically check the versions of all the project's npm package dependencies. If any are found to be outdated, it will submit a pull request to update them.
Add a task and GitHub Actions workflow to check for problems with npm configuration files. On every push and pull request that affects relevant files, and periodically a GitHub Actions workflow will run the task to: - Validate package.json against its JSON schema. - Check for forgotten package-lock.json syncs.
Whenever one of the recognized license file names are modified in the repository, the workflow runs to check whether the license can be recognized and whether it is of the expected type. GitHub has a useful automated license detection system that determines the license type used by a repository, and surfaces that information in the repository home page, the search web interface, and the GitHub API. This license detection system requires that the license be defined by a dedicated file with one of several standardized filenames and paths. GitHub's license detection system uses the popular licensee tool, so this file also serves to define the license type for any other usages of licensee, as well as to human readers of the file. For this reason, and to ensure it remains a valid legal instrument, it's important that there be no non-standard modifications to the license file or collisions with other supported license files. This workflow ensures that any changes which would change the license type or which license file is used by the detection are caught automatically.
There are differences in the filename restrictions between operating systems. The use of filenames that are not valid on one operating system in the project will cause problems for contributors or users (e.g., not possible to check out the repository). Tasks are added to check for non-portable filenames: - Presence of characters prohibited by an operating system in filenames - Use of filenames reserved by an operating system Tasks are also added to check for problems with symbolic links ("symlinks") contained in the project: - Broken symlinks - Circular symlinks A GitHub Actions workflow is included to run the tasks on any change to the project files in order to avoid the introduction of problems with the project filesystem, and periodically in order to catch breakage caused by external changes.
A task is added to check whether the repository's files are formatted according to the conventions defined in the project `.editorconfig` file. A GitHub Actions workflow runs the task on every push, pull request, and periodically.
Add a task to tidy the project's Go module dependency manifest. On every push and pull request that affects relevant files, the added Github Actions workflow will run the task and then check for an out of sync Go module dependencies manifest.
Tasks are added to check the repository's Markdown files for problems: - Use markdownlint to check for common problems and formatting. - Use markdown-link-check to check for broken links. On every push and pull request that affects relevant files, and periodically, a GitHub Actions workflow will run these tasks. The Arduino tooling Markdown style is defined by the `.markdownlint.yml` file. In the event the repository contains externally maintained Markdown files, markdownlint can be configured to ignore them via a `.markdownlintignore` file: https://github.com/igorshubovych/markdownlint-cli#ignoring-files markdown-link-check is configured via the `.markdown-link-check.json` file: https://github.com/tcort/markdown-link-check#config-file-format
A task and GitHub Actions workflow are added to provide compliance with the standardized code formatting style provided by the Prettier formatter tool. On every push and pull request that affects relevant files, the workflow runs the task to check whether the formatting of supported files is compliant with the Prettier style.
Add a task to lint the project's YAML files using the yamllint tool. On every push and pull request that affects relevant files, a GitHub Actions workflow will run the task to check the YAML files of the repository for issues. The .yamllint.yml file is used to configure yamllint: https://yamllint.readthedocs.io/en/stable/configuration.html
Dependabot will periodically check the versions of all the project's Python package dependencies. If any are found to be outdated, it will submit a pull request to update them.
The project's Python package dependencies are managed using the Poetry tool. Tasks and a GitHub Actions workflow are added to maintain and check for problems in the Poetry configuration files. The tasks provide the following operations: - Check for invalid data structure of pyproject.toml - Check for out of sync poetry.lock file These tasks are ran by the GitHub Actions workflow on any push or pull request that modifies relevant files, and periodically to check for breakage caused by external changes.
On every push or pull request that affects the repository's Taskfiles, and periodically, validate them against the JSON schema.
Add a task to validate the project's GitHub Actions workflows. On every push or pull request that affects the repository's GitHub Actions workflows, and periodically, a GitHub Actions workflow will run the task validate the workflows against the JSON schema.
Add tasks and a GitHub Actions workflow to check for commonly misspelled words. On every push, pull request, and periodically, use codespell to check for commonly misspelled words. In the event of a false positive, the problematic word should be added, in all lowercase, to the `ignore-words-list` field of `.codespellrc`. Regardless of the case of the word in the false positive, it must be in all lowercase in the ignore list. The ignore list is comma-separated with no spaces.
On every push that changes relevant files, and periodically, configure the repository's issue and pull request labels according to the universal, shared, and local label configuration files.
Add a task and GitHub Actions workflow to lint JavaScript code using ESLint. On every push and pull request that affects relevant files, and periodically, the workflow will run the task to check for problems with the repository's JavaScript files. ESLint is configured via the .eslintrc.yml file: https://eslint.org/docs/user-guide/configuring/configuration-files
A task and GitHub Actions workflows are added to use eslint with the eslint-plugin-jsonc plugin to lint the JSON files of the repository. On every push and pull request that affects relevant files, and periodically, the workflow will run the task. eslint is configured via the .eslintrc.yml file: https://eslint.org/docs/user-guide/configuring/configuration-files
The project's Python package dependencies are configured via the pyproject.toml file. Since this file is edited manually, it will be useful to provide infrastructure for standardizing the code formatting and validating compliance with that standard. This is done by the installation of the "prettier-plugin-toml", which adds support for TOML language to the Prettier formatting tool. The `general:format-prettier` task will now also format the TOML files of the repository. The "Check Prettier Formatting" workflow will enforce the formatting compliance.
A task and GitHub Actions workflow are added to use run the Jest-based tests for the project's JavaScript or TypeScript code. On every push and pull request that affects relevant files, and periodically, the workflow will run the repository's TypeScript/JavaScript tests and upload the code coverage data to the Codecov service. Codecov will comment a coverage report on all pull requests that trigger the workflow. This report will help the contributor and reviewers to identify any introduced code that isn't being covered by tests.
A task and GiHub Actions Workflow is added to check for problems in the project's EJS template files using the ejs-lint tool. On any push or pull request that modifies relevant files, and periodically, the workflow will run the task.
Bumps [eslint](https://github.com/eslint/eslint) from 8.57.0 to 9.9.0. - [Release notes](https://github.com/eslint/eslint/releases) - [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) - [Commits](eslint/eslint@v8.57.0...v9.9.0) --- updated-dependencies: - dependency-name: eslint dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
The following labels could not be found: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is blocked due to the lack of support for eslint 9.x by the eslint-config-airbnb-base
package:
Looks like eslint is no longer a dependency, so this is no longer needed. |
@dependabot recreate |
Looks like this PR is closed. If you re-open it I'll rebase it as long as no-one else has edited it (you can use |
@dependabot reopen |
Dependabot tried to reopen this PR, but was told that the target branch has been deleted (and therefore that this PR couldn't be reopened). |
Bumps eslint from 8.57.0 to 9.9.0.
Release notes
Sourced from eslint's releases.
... (truncated)
Changelog
Sourced from eslint's changelog.
... (truncated)
Commits
0dd3863
9.9.02e5ba77
Build: changelog update for 9.9.0461b2c3
chore: upgrade to@eslint/[email protected]
(#18765)59dba1b
chore: package.json update for@eslint/js
releasefea8563
chore: update dependency@eslint/core
to ^0.3.0 (#18724)41d0206
feat: Add support for TS config files (#18134)aac191e
chore: update dependency@eslint/json
to ^0.3.0 (#18760)9fe068c
docs: how to author plugins with configs that extend other configs (#18753)b97fa05
chore: update wdio dependencies for more stable tests (#18759)3a4eaf9
feat: add suggestion torequire-await
to removeasync
keyword (#18716)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)