Skip to content

Conversation

@yueny2020
Copy link
Contributor

Problem

  • not expose MCP feature before public release

Solution


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@yueny2020 yueny2020 requested a review from a team as a code owner June 2, 2025 22:32
@github-actions
Copy link

github-actions bot commented Jun 2, 2025

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@yueny2020 yueny2020 enabled auto-merge June 2, 2025 22:38
@yueny2020 yueny2020 merged commit 0999e72 into aws:master Jun 3, 2025
30 of 31 checks passed
@yueny2020 yueny2020 deleted the revert branch June 11, 2025 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants