Skip to content

AWS Transform Kiro Power sync (post cli-3.3.0)#158

Merged
nadetastic merged 1 commit into
kirodotdev:mainfrom
jdonboch:aws-transform-release-post-cli-3.3.0
Jul 1, 2026
Merged

AWS Transform Kiro Power sync (post cli-3.3.0)#158
nadetastic merged 1 commit into
kirodotdev:mainfrom
jdonboch:aws-transform-release-post-cli-3.3.0

Conversation

@jdonboch

Copy link
Copy Markdown
Contributor

Promotes ATXKiroPower/mainline changes merged since the cli-3.3.0 tag for the continuous-modernization steering set (6 files: EC2/Batch execution, scheduling, remediation, source).

Draft — pending: author sign-off and version bump (POWER.md).

Promote ATXKiroPower/mainline continuous-modernization steering updates
merged since the cli-3.3.0 tag (EC2/Batch execution, scheduling,
remediation, source handling).

Bump POWER.md version 2.1.2 -> 2.2.0 (minor; feature release).
@jdonboch jdonboch force-pushed the aws-transform-release-post-cli-3.3.0 branch from cf13009 to b29e0e3 Compare June 30, 2026 19:53
@jdonboch jdonboch marked this pull request as ready for review June 30, 2026 20:07

@carolabadeer carolabadeer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General question - are the mainframe changes in the corresponding agent plugin PR not mirrored in the Kiro power? awslabs/agent-plugins#209

@jdonboch

Copy link
Copy Markdown
Contributor Author

General question - are the mainframe changes in the corresponding agent plugin PR not mirrored in the Kiro power? awslabs/agent-plugins#209

This is because the M2 changes are already merged/present in this repo

@nadetastic nadetastic merged commit edd0fca into kirodotdev:main Jul 1, 2026
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.

6 participants