chore(deps-dev)(deps-dev): bump @eslint/js from 9.39.1 to 10.0.1 in /web#10
chore(deps-dev)(deps-dev): bump @eslint/js from 9.39.1 to 10.0.1 in /web#10dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@eslint/js](https://github.com/eslint/eslint/tree/HEAD/packages/js) from 9.39.1 to 10.0.1. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](https://github.com/eslint/eslint/commits/v10.0.1/packages/js) --- updated-dependencies: - dependency-name: "@eslint/js" dependency-version: 10.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
NPM Vulnerability Scan Results - e2e
Click to see details |
Go Vulnerability Scan ResultsFound 299 vulnerability/vulnerabilities Details:=== Symbol Results === Vulnerability #1: GO-2026-4603 Vulnerability #2: GO-2026-4602 Vulnerability #3: GO-2026-4601 Vulnerability #4: GO-2026-4394 Vulnerability #5: GO-2026-4337 Your code is affected by 5 vulnerabilities from 1 module and the Go standard library. |
Docker Image Scan Results - Dockerfile.indexerImage:
Click to see details |
Docker Image Scan Results - Dockerfile.apiImage:
Click to see details |
Bumps @eslint/js from 9.39.1 to 10.0.1.
Release notes
Sourced from
@eslint/js's releases.... (truncated)
Commits
84fb885chore: package.json update for@eslint/jsrelease1f66734chore: addeslinttopeerDependenciesof@eslint/js(#20467)f3fbc2fchore: set@eslint/jsversion to 10.0.0 to skip releasing it (#20466)b4b3127chore: package.json update for@eslint/jsrelease0b14059chore: package.json update for@eslint/jsreleasefa31a60feat!: addnameto configs (#20015)1e2cad5chore: package.json update for@eslint/jsrelease454a292feat!: updateeslint:recommendedconfiguration (#20210)c6358c3feat!: Require Node.js^20.19.0 || ^22.13.0 || >=24(#20160)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)