build(deps-dev): bump eslint-config-next from 16.2.6 to 16.3.4 in /frontend - #5
Closed
dependabot[bot] wants to merge 6 commits into
Closed
dependabot[bot] wants to merge 6 commits into
dependabot[bot] wants to merge 6 commits into
Conversation
Rename project from Agentic-Quant to QuantDebate. Added: - High-quality English and Chinese README with architecture diagrams - CONTRIBUTING.md with development setup and coding standards - CODE_OF_CONDUCT.md (Contributor Covenant 2.0) - SECURITY.md with responsible disclosure policy - CHANGELOG.md following SemVer - GitHub issue templates (bug report, feature request) - Pull request template - Dependabot configuration (pip, npm, GitHub Actions) - CI workflow (lint, test, frontend build) - DevContainer configuration for GitHub Codespaces - scripts/dev for one-command development startup - .dockerignore for Docker builds - NOTICE file for third-party attributions - pyproject.toml with full PyPI metadata Changed: - All code comments translated from Chinese to English - properties.env.example comments translated to English - .gitignore updated to exclude internal docs (bugs/, plans/, archive/) - CLAUDE.md rewritten as public project guide (excluded from tracking) Removed from tracking: - CLAUDE.md (AI assistant config, excluded via .gitignore) - bugs/ (internal bug tracker) - plans/unfixed-bugs/ (internal planning docs) - archive/ (deprecated code)
Added: - CHANGELOG.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md - quick_ask/ LangGraph pipeline agents - docs/ architecture and design documents - frontend/ source code (excluding .next build artifacts) - skills/ SKILL.md documents - test/ test suite - belief/ trading belief models - knowledge/ rules and findings - mcp/ MCP integration - notification/ notification channels - reports/ report generation - storage/ persistence layer Note: some files in frontend/.next/ and node_modules/ are corrupted at the macOS filesystem level (APFS Resource deadlock avoided error). These are build artifacts and dependencies, not source code.
Added remaining modules that were previously blocked by corrupted files: - docs/ architecture and design documents (partial) - belief/ trading belief models and presets - knowledge/ rules and findings CRUD - mcp/ MCP integration (BaseTool, ToolRegistry, MCPClientManager) - notification/ channel adapters - test/ remaining test files
Added frontend/ source code, skills/ SKILL.md documents, and remaining documentation files. Some files in frontend/ and skills/ are corrupted at the macOS APFS level (Resource deadlock avoided) and could not be added. These are primarily build artifacts (.next/) and third-party reference docs (Vibe-Trading/). The following directories remain partially untracked due to filesystem corruption: frontend/ (source files added, build artifacts skipped), skills/ (working files added, corrupted references skipped).
Added all remaining project files that were previously blocked by macOS iCloud file synchronization (dataless/compressed flags). Resolved by using brctl download to force local file retrieval. Added: - skills/ all SKILL.md documents (76 files across 10 categories) - reports/ academic deliverables (proposal, interim report, defense prep) - plans/ development plans and broker integration docs - test/ remaining test files - All previously corrupted source files now properly tracked This completes the full project file tracking. Total: 386 + 267 = 653 files tracked across 5 commits.
Bumps [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) from 16.2.6 to 16.3.4. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](https://github.com/vercel/next.js/commits/v16.3.4/packages/eslint-config-next) --- updated-dependencies: - dependency-name: eslint-config-next dependency-version: 16.3.4 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/frontend/eslint-config-next-16.3.4
branch
September 8, 2026 14:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps eslint-config-next from 16.2.6 to 16.3.4.
Release notes
Sourced from eslint-config-next's releases.
... (truncated)
Commits
299180dv16.3.4a9a1cb7v16.3.3d0ac882v16.3.23d32eb8v16.3.1d73f562v16.3.04fd843fv16.3.0-canary.1079480f7fv16.3.0-canary.106a8dcd25v16.3.0-canary.10538f0cdev16.3.0-canary.104f3edea1v16.3.0-canary.103Dependabot 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)