Skip to content

chore(deps-dev): bump eslint from 9.39.4 to 10.6.0 #230

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.

Sign up for GitHub

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

Open
dependabot wants to merge 3 commits into
base: main
Choose a base branch
from
Open

chore(deps-dev): bump eslint from 9.39.4 to 10.6.0 #230

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
13f6db3
feat(eslint)!: switch JSX a11y linting to eslint-plugin-jsx-a11y-x
jhnns Jul 7, 2026
4007f88
docs(ai): add comment style and commit message conventions
jhnns Jul 13, 2026
b71013f
chore(deps-dev): bump eslint from 9.39.4 to 10.6.0
dependabot[bot] Jul 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ai/coding-styleguide-js-ts.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,7 @@ globs: **/*.js, **/*.ts, **/*.mjs, **/*.cjs, **/*.mts, **/*.cts
- Use comments to explain why, invariants, constraints, and non-obvious trade-offs
- Do not write comments that only restate what the code already makes obvious
- Add short contract comments only for complex or high-impact exports. Focus on purpose, guarantees, and important caveats.
- **Comments:** no bare `/* */` block comments. Use `//` for inline notes; use JSDoc (`/** */`) for file-level comments (with `@file`) and when documenting an exported symbol, prop, or function.

## Testing

Expand Down
1 change: 1 addition & 0 deletions ai/rules.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ See [Coding Styleguide Shell Scripts](./coding-styleguide-sh.mdc)
- Write integration or e2e tests for more complex functions/classes/components
- Prefer staged validation for non-trivial tasks: run focused checks after meaningful changes, then run broader lint/type/test checks before handoff. For trivial tasks, a single final validation is acceptable.
- Adjust documentation both in comments and markdown files once you're done
- Use [Conventional Commits](https://www.conventionalcommits.org/) for commit messages

## Consumer-repo uncertainty protocol

Expand Down
Loading
Loading