chore(deps): Update 7 dependencies - Round 2#56
Merged
semanticintent merged 1 commit intomasterfrom Nov 25, 2025
Merged
Conversation
Dependencies updated: - agents: 0.2.20 → 0.2.23 - @modelcontextprotocol/sdk: 1.20.2 → 1.22.0 (MCP SDK update) - @biomejs/biome: 2.3.2 → 2.3.7 - @cloudflare/vitest-pool-workers: 0.10.3 → 0.10.10 - @types/node: 24.10.0 → 24.10.1 - wrangler: 4.45.3 → 4.50.0 GitHub Actions: - actions/checkout: v5 → v6 Note: Vitest v4 upgrade (vitest, @vitest/coverage-v8, @vitest/ui) postponed - waiting for @cloudflare/vitest-pool-workers to support v4. All tests passing (109/109) Type-check: ✓
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
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.
Dependencies updated:
GitHub Actions:
Note: Vitest v4 upgrade (vitest, @vitest/coverage-v8, @vitest/ui) postponed - waiting for @cloudflare/vitest-pool-workers to support v4.
All tests passing (109/109)
Type-check: ✓
🎯 Semantic Intent
What semantic problem does this PR solve?
Brief description of the semantic intent behind this change.
📝 Description
What changed and why?
Detailed explanation of the changes and their business value.
🔗 Related Issues
Closes #(issue)
🏗️ Type of Change
📋 Architectural Impact
Which layers are affected?
src/domain/)src/application/)src/infrastructure/)src/presentation/)✅ Checklist
Before submitting:
npm test)npm run type-check)npm run format)🧪 Testing
How has this been tested?
Describe the tests you ran:
Test configuration:
📸 Screenshots (if applicable)
Add screenshots for UI changes or visual improvements.
🎨 Code Quality
Semantic Intent Documentation:
Architecture:
🔍 Breaking Changes
Does this PR introduce breaking changes?
If yes, describe migration path:
📚 Additional Context
Add any other context about the PR here.
🤝 Reviewer Notes
Specific areas to review:
By submitting this PR, I confirm: