Github Releases

Automated workflow for GitHub that checks for new releases every 10 minutes, extracts relevant information, and sends notifications to Slack. It efficiently categorizes updates into features, fixes, and others, ensuring timely communication of important changes and enhancing team awareness.

7/8/2025
24 nodes
Complex
schedulecomplexsplitinbatchesschedule triggerslacklangchainsticky noteredisrssfeedreadautomationadvancedcronlogicconditionalcommunicationnotification
Categories:
Communication & MessagingSchedule TriggeredComplex WorkflowData Processing & Analysis
Integrations:
SplitInBatchesSchedule TriggerSlackLangChainSticky NoteRedisRssFeedRead

Target Audience

This workflow is ideal for:
- Developers: Who want to automate the tracking of GitHub releases for multiple repositories.
- Project Managers: Looking to stay updated on the latest features and fixes from repositories they manage.
- DevOps Teams: Needing to streamline communication about software updates within their organization.
- Tech Enthusiasts: Interested in following the latest developments in open-source projects.

Problem Solved

This workflow addresses the challenge of manually monitoring GitHub releases across multiple repositories. It automates the process of checking for new releases, extracting relevant information, and notifying team members via Slack, thereby saving time and ensuring that no important updates are missed.

Workflow Steps

  • Trigger: The workflow is triggered every 10 minutes between 9 AM and 11 PM daily using a Cron Trigger.
    2. Fetch GitHub Config: It retrieves a list of repositories to monitor from the GitHub Config node.
    3. Loop Through Repositories: For each repository, it uses the Split In Batches node to process them one by one.
    4. Read RSS Feed: The workflow reads the RSS feed for releases from the GitHub repository using the RSS for Release node.
    5. Check for Errors: It checks if there were any errors in fetching the data, using the If No Error node.
    6. Redis Cache: It retrieves the last known release ID from Redis to compare against the current release.
    7. Determine New Releases: If a new release is detected (i.e., the ID is different), it processes the release information.
    8. Information Extraction: The Information Extractor node analyzes the release notes, filtering and categorizing the changes into features, fixes, and other relevant notes.
    9. Format Date: The release publication date is formatted for better readability.
    10. Send Notifications: Finally, the workflow sends a formatted message to a designated Slack channel using the Send Message node, notifying the team of the new release.

    • Customization Guide

  • Modify GitHub Repositories: Update the GitHub Config node to add or remove repositories you wish to monitor. Each entry should include a name and github path (e.g., owner/repo).
    2. Adjust Cron Schedule: Change the Cron Trigger settings to modify how frequently the workflow checks for updates. The current setting checks every 10 minutes.
    3. Customize Slack Notifications: In the Send Message node, adjust the message format or the target Slack channel ID to tailor notifications to your team's needs.
    4. Enhance Information Extraction: Review and modify the Information Extractor node's system prompt to change how the AI extracts and translates information from release notes, adapting it to different languages or formats as needed.