version: v1.0.0-beta4 - Teams message management with deletion limitation docs
- Document Teams API limitation for channel message deletion - Clearly state this is a platform limitation, not an application bug - Provide workarounds for users
This commit is contained in:
@@ -2,6 +2,19 @@
|
||||
|
||||
All notable changes to this project will be documented in this file.
|
||||
|
||||
## v1.0.0-beta4 - 2025-12-20
|
||||
|
||||
- Teams Message Management
|
||||
- Added UI (`frontend/teams-messages.html`) to load and review Teams channel messages with job details.
|
||||
- Features: Auto-load via URL params, auto-select up to 50 messages, preview job card details, collapsible JSON.
|
||||
- **Known Limitation**: Message deletion is not supported by Microsoft Teams Graph API for public channels (HTTP 405).
|
||||
- This is a platform limitation, not an application error.
|
||||
- Workaround 1: Delete messages directly from Teams client (right-click → Delete).
|
||||
- Workaround 2: Use delegated user token with `ChatMessage.ReadWrite.All` permission (requires Azure AD configuration).
|
||||
- Updated error handling to clearly explain Teams API limitations to users.
|
||||
- Ops
|
||||
- Enhanced error logging in server delete endpoint to capture full error details and distinguish between API errors and Teams platform limitations.
|
||||
|
||||
## v1.0.0-beta3 - 2025-12-20
|
||||
|
||||
- Teams Notifications
|
||||
|
||||
Reference in New Issue
Block a user