feat: Feature Sept 2025 - MACAE V3 #418
Merged
Merged
Conversation
Moves plan approval request and waiting state management from PlanChat and PlanPanelRight into PlanPage, passing them as props. This centralizes WebSocket handling and plan state, simplifies component logic, and ensures consistent plan approval UI updates across components.
Introduces a new StreamingBufferMessage component to render live agent message streams in PlanChat. Updates PlanPage and WebSocketService to handle and buffer streaming agent messages, improving real-time feedback during plan generation.
Introduces support for streaming agent messages in the plan chat by adding the AgentMessageData model, a new StreamingAgentMessage renderer, and updating PlanChat and PlanPage to handle and display agent messages. This enhances visibility into agent activity during plan generation.
Macae v3 fr dev 92
docs: Add note on role assignment for existing Azure AI Foundry access
… module configuration
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Removed duplicate lines explaining the DeploymentNotFound issue and its avoidance.
fix: Restrict Supported Azure Regions and Add Configurable Zone Redundancy for Cosmos DB
fix: Restrict Supported Azure Regions and Add Configurable Zone Redundancy for Cosmos DB
fix: updated the main_custom for cosmos error
fix: merge Cosmos DB issue fixes from dev into main
fix: Updated the package-lock.json file to resolve the build issue
fix: Added the user_id explicitly to get the completed task
docs: Additional troubleshooting steps
Roopan-Microsoft
changed the title
Replaced the agent_flow.png and architecture.png images in the documentation to reflect updated diagrams. This improves clarity and accuracy in the project's README visualizations.
Update agent flow and architecture diagrams
fix: plan activities that mention agents, Logging fixes, clean-up
docs: clarify navigation by adding step to enter 'infra' directory before 'scripts'
chore: merging dev changes to main branch
Roopan-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
chore: downmerge main to v3 feature branch
fix: updated the pipeline and bicep changes
marktayl1
approved these changes
Sep 22, 2025
marktayl1
left a comment
marktayl1
left a comment
Contributor
There was a problem hiding this comment.
This seems to be the branch of vip we have been working in. I assume that it was tested fully by Persistent yesterday. Looking at last nights changes these look okay but tested by Persistent.
Roopan-Microsoft
approved these changes
Sep 22, 2025
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
deepammi
pushed a commit
to deepammi/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator
that referenced
this pull request
Dec 7, 2025
feat: Feature Sept 2025 - MACAE V3
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
9 participants
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.
Purpose
This pull request introduces new deployment workflows for v2 environments and updates the existing v3 deployment workflows to support new branches and image tags. The main changes include the addition of
.github/workflows/deploy-v2.ymland.github/workflows/deploy-waf-v2.ymlfor v2 deployments, enhancements to resource cleanup and notification handling, and updates to v3 workflows to support thedev-v3branch and new image tags.New Deployment Workflows for v2:
.github/workflows/deploy-v2.ymlto automate deployment, resource cleanup, quota checks, and notifications for themacae-v2anddevbranches, including scheduled and manual triggers. This workflow also runs end-to-end tests and cleans up resources after deployment..github/workflows/deploy-waf-v2.ymlfor WAF deployments on v2, supporting scheduled and push triggers for themacae-v2branch, with similar resource management and notification features.Enhancements to v3 Deployment Workflows:
.github/workflows/deploy.ymland.github/workflows/deploy-waf.ymlto reflect "v3" in workflow names and support the newdev-v3branch for deployments. [1] [2] [3].github/workflows/deploy.ymlto uselatest_v3anddev_v3tags for themainanddev-v3branches, respectively, improving clarity and separation between environments.createdBy="Pipeline"parameter to the Bicep deployment step in.github/workflows/deploy-waf.ymlfor better traceability of automated deployments.Does this introduce a breaking change?