App Manifest Schema Update v1.26
Latest Schema Commit: 48e69ec
🎯 Impacted Properties We Support
The following properties used in our templates have been updated and require attention:
description ✅ NON-BREAKING
Change: Added a 'features' array property with constraints (minItems: 1, maxItems: 3) and required 'title' and 'description' fields for each feature.
Impact: Business logic may need to support and validate the new 'features' array. If not handled, submissions missing this property or not meeting constraints may fail validation. Integration must ensure feature descriptions are provided and formatted correctly.
composeExtensions ✅ NON-BREAKING
Change: Authorization 'authType' enum expanded to include 'oAuth2.0'; new 'oAuthConfiguration' object required when 'authType' is 'oAuth2.0'.
Impact: Business logic and integrations must support the new 'oAuth2.0' authentication type and ensure correct handling and population of 'oAuthConfiguration' when applicable. Existing flows may need updates to accommodate OAuth scenarios.
copilotAgents 🚨 BREAKING
Change: Changed from 'oneOf' with required fields to an empty 'anyOf' array.
Impact: Validation logic may break or become less restrictive, potentially allowing invalid or incomplete copilotAgents data. Business rules relying on required agent types may need revision to ensure data integrity.
📋 Action Required
Please update the following files in each template repository:
Note: Ensure all impacted properties listed above are properly updated according to the new schema requirements.
🔗 Related Work Item
Azure DevOps Work Item
This issue was automatically generated by the Dependency Manager.
App Manifest Schema Update v1.26
Latest Schema Commit: 48e69ec
🎯 Impacted Properties We Support
The following properties used in our templates have been updated and require attention:
description✅ NON-BREAKINGChange: Added a 'features' array property with constraints (minItems: 1, maxItems: 3) and required 'title' and 'description' fields for each feature.
Impact: Business logic may need to support and validate the new 'features' array. If not handled, submissions missing this property or not meeting constraints may fail validation. Integration must ensure feature descriptions are provided and formatted correctly.
composeExtensions✅ NON-BREAKINGChange: Authorization 'authType' enum expanded to include 'oAuth2.0'; new 'oAuthConfiguration' object required when 'authType' is 'oAuth2.0'.
Impact: Business logic and integrations must support the new 'oAuth2.0' authentication type and ensure correct handling and population of 'oAuthConfiguration' when applicable. Existing flows may need updates to accommodate OAuth scenarios.
copilotAgents🚨 BREAKINGChange: Changed from 'oneOf' with required fields to an empty 'anyOf' array.
Impact: Validation logic may break or become less restrictive, potentially allowing invalid or incomplete copilotAgents data. Business rules relying on required agent types may need revision to ensure data integrity.
📋 Action Required
Please update the following files in each template repository:
manifest.json.tplmanifest.local.json.tpl(if applicable)manifest.dev.json.tpl(if applicable)Note: Ensure all impacted properties listed above are properly updated according to the new schema requirements.
🔗 Related Work Item
Azure DevOps Work Item
This issue was automatically generated by the Dependency Manager.