Skip to content

fix(compat): address v0 project follow-ups - #2593

Merged
notgitika merged 1 commit into
aws:refactorfrom
notgitika:fix/v0-compat-followups
Oct 13, 2026
Merged

notgitika merged 1 commit into
aws:refactorfrom
notgitika:fix/v0-compat-followups

Conversation

@notgitika

Copy link
Copy Markdown
Contributor

Description

Addresses the remaining actionable review feedback from #2575 while keeping the compatibility layer small.

  • delegate v0 deployment through the latest v0 release (@aws/agentcore@0) instead of pinning one patch version
  • forward the v1-resolved AWS region to delegated v0 deployment, including first deploy with no targets configured
  • omit toolRuntimes when v0 explicitly contains an empty mcpRuntimeTools array
  • remove the duplicate LegacyExtras copy; legacy.v0Spec remains the source of truth for v0-only collections

Targeted replacement guidance for removed v0 commands is intentionally excluded until the wording is agreed.

Related Issue

Closes #2592

Documentation PR

Not applicable; this tightens internal compatibility behavior without adding a new user workflow.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update
  • Other (please describe):

Testing

  • I ran bun test — 4,105 passed
  • Relevant E2E coverage is not applicable; handler/subprocess regression tests cover the changed handoff, and the published v0 CLI was smoke-tested with deploy --region.
  • I ran bun run typecheck
  • I ran bun run lint:check
  • I ran bun run format:check
  • I ran bun run build
  • src/assets/ was not modified

Checklist

  • I have read the CONTRIBUTING document
  • I have added tests that prove the fixes are effective
  • Documentation changes are not needed for these internal compatibility corrections
  • No new documentation example is needed
  • My changes generate no new warnings
  • There are no dependent changes that must be published first

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@github-actions github-actions Bot added the size/m PR size: M label Oct 13, 2026
@agentcore-devx-automation agentcore-devx-automation Bot added agentcore-harness-reviewing AgentCore Harness review in progress claude-security-reviewing Claude Code /security-review in progress labels Oct 13, 2026
@agentcore-devx-automation

Copy link
Copy Markdown
Contributor

Claude Security Review: no high-confidence findings. (run)

@agentcore-devx-automation agentcore-devx-automation Bot removed claude-security-reviewing Claude Code /security-review in progress agentcore-harness-reviewing AgentCore Harness review in progress labels Oct 13, 2026
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.33%. Comparing base (3207575) to head (654d36f).

Additional details and impacted files
@@            Coverage Diff            @@
##           refactor    #2593   +/-   ##
=========================================
  Coverage     96.33%   96.33%           
=========================================
  Files           671      671           
  Lines         51319    51321    +2     
=========================================
+ Hits          49437    49439    +2     
  Misses         1882     1882           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@notgitika
notgitika merged commit 0c43c32 into aws:refactor Oct 13, 2026
20 of 22 checks passed
@notgitika
notgitika deleted the fix/v0-compat-followups branch October 13, 2026 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/m PR size: M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants