- Enhanced the GmailMessageAddedEvent class to support additional attachment types and improved metadata extraction.
- Updated methods for handling inline content and external links, ensuring better integration with attachments.
- Revised the output schema in the YAML to include new fields for attachment metadata, improving clarity and usability.
- Updated the GmailMessageAddedEvent class to support uploading up to 20 attachments, with improved handling for inline content and external links.
- Introduced new methods for extracting links from HTML and text, allowing for better integration of external attachments.
- Modified the output schema in the YAML to reflect changes in attachment metadata, including renaming fields for clarity.
- Renamed the trigger from "Gmail Trigger" to "gmail_trigger" in the manifest for consistency.
- Improved the GmailMessageAddedEvent class by adding methods for processing attachments, including handling inline data and file uploads.
- Updated the output schema in the YAML to include new fields for attachment metadata, enhancing the event's data structure.
- Renamed the trigger label from "Gmail" to "Gmail Trigger" for clarity.
- Updated the manifest to reflect the new naming convention and removed the old `gmail.yaml` configuration file.
- Deleted the `gmail.py` provider file as part of the cleanup process, streamlining the trigger's implementation.
- Enhanced error handling by preserving the original exception context when raising EventIgnoreError.
- This change ensures better debugging and traceability of errors during event processing.
- Deleted the GmailMessageEvent class and its associated YAML configuration as part of the cleanup process.
- Updated the GmailTrigger class to remove references to the unified message event, focusing on individual message addition and deletion events.
- Adjusted documentation to reflect the removal of the unified event handling.
- Updated the GmailMessageEvent class to handle both added and deleted messages, improving event management.
- Introduced a new `cancelled` field in TriggerInvokeEventResponse to indicate event cancellation.
- Enhanced error handling with EventIgnoreError for cases with no relevant messages.
- Updated YAML documentation to reflect changes in event behavior and output schema.
- Enhanced the README with detailed setup steps for Google Cloud project and OAuth configuration.
- Added images for better clarity on GCP setup.
- Removed deprecated parameters like `watch_email` and `topic_name` from the YAML schema.
- Introduced label-based filtering in event handling for better message management.
- Simplified error message formatting for unrecognized star actions using f-strings.
- Removed the unused _fetch_parameter_options method and its associated imports to clean up the code.
- Introduced a new method _fetch_parameter_options to retrieve parameter options based on credential type and access tokens.
- Enhanced the handling of unauthorized credentials by providing a default option when no valid credentials are available.
- Updated imports to include necessary entities for the new functionality.
- Simplified error message formatting for unrecognized star actions.
- Removed the unused _fetch_parameter_options method and its associated imports to streamline the code.
- Updated the _MAX_PAGES constant to allow for more pages of changes to be fetched.
- Removed the time constraint on fetching changes to improve efficiency.
- Renamed cursor fields in the payload from 'cursor_before' and 'cursor_after' to 'cursor_start' and 'cursor_end' for clarity.
- Added descriptions for new cursor fields in the YAML output schema to improve documentation.
- Updated _on_event method to accept a Request object and additional parameters.
- Modified payload processing to extract and structure changes, accounts, cursors, and received timestamp.
- Removed unnecessary cursor fields from the output schema in YAML.
- Updated version in manifest.yaml to 1.3.9.
- Added optional 'scope' field in github.yaml for OAuth API access with default value and help documentation.
- Updated version in pyproject.toml and requirements.txt to 0.6.0b13.
- Changed 'raw_http_response' to 'response' in TriggerDispatchResponse model for clarity.
- Updated GitHub trigger manifest version to 1.3.8.
Based on real webhook data, added comprehensive output schema including:
- Detailed file object properties (id, name, mimeType, createdTime, modifiedTime, etc.)
- Nested user objects for owners and lastModifyingUser
- Complete subscription object with channel metadata and user details
- Proper descriptions for all fields
This ensures the event output accurately reflects the actual Google Drive API response structure.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added user_id field to EventDispatch and TriggerDispatchResponse models to track the user triggering events.
- Updated GitHub trigger provider to include user_id in event dispatching.
- Modified star event parameters in YAML to simplify naming conventions from "star_created" and "star_deleted" to "created" and "deleted".
- Bumped plugin version in manifest.yaml from 1.3.5 to 1.3.6 to reflect these changes.
- Renamed "Message Received" to more specific labels:
- message_edited.yaml → "Message Edited"
- business_message_received.yaml → "Business Message Received"
- business_message_edited.yaml → "Business Message Edited"
- channel_post_created.yaml → "Channel Post Created"
- channel_post_edited.yaml → "Channel Post Edited"
Now all event labels are unique and clearly describe their specific purpose.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Applied chat_boost event pattern to all 20 Telegram event handlers
- All event classes now inherit from both TelegramUpdateEvent and Event
- Preserved custom _build_variables implementations where present (e.g., message_received.py)
- Simple events now follow the minimal pattern with just update_key defined
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>