Repository navigation
feat(aws-devops-agent): rename release readiness review to code change risk analysis - #211
Open
amznUjjwalpa wants to merge 1 commit into
Open
amznUjjwalpa wants to merge 1 commit into
amznUjjwalpa wants to merge 1 commit into
Conversation
…e risk analysis Release readiness review is now called code change risk analysis. - Call the code change risk analysis tools (create_code_change_risk_analysis, list_code_change_risk_analyses, cancel_code_change_risk_analysis, get_code_change_risk_analysis_report). The server picks the task type. - Use the new name when talking to users, and still recognize the old one. - Find an earlier analysis with list_code_change_risk_analyses. - The aws-mcp fallback creates CODE_CHANGE_RISK_ANALYSIS tasks.
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.
Description
Release readiness review is now called code change risk analysis (CCRA). This updates the
aws-devops-agentpower to the new name and tools.create_code_change_risk_analysis,list_code_change_risk_analyses,cancel_code_change_risk_analysisandget_code_change_risk_analysis_report. The server picks the task type, so the steering no longer names one.list_code_change_risk_analyses, and adds the read-only list tool toautoApprove.CODE_CHANGE_RISK_ANALYSIStasks.steering/release-readiness.md, the spec-completion hook file), so existing installs and references keep working.The release readiness review tools stay on the MCP server as aliases of the new ones, so older copies of this power keep working.
Testing
Ran the MCP server's new tools against a gamma agent space: create, list (both task types, newest first, paging), cancel and report, through both the new and the old tool names.