Automated release diffs for GitLab tags

Problem Context

Developers using GitLab with semantic versioning (e.g., v89.4.3. need to compare code changes between major releases (e.g., v89.0.0 → v90.0.0). They rely on tags to mark releases but struggle to see the actual code differences between versions, forcing them to manually review commit logs or change logs, which is inefficient and error-prone.

Pain Points

Users waste time manually creating branches and merge requests (MRs) to compare releases, leading to delays in identifying critical changes. Their current workaround—generating a branch from the new tag and merging it into the old tag—is clunky and doesn’t provide a clean, automated way to visualize differences. They also risk missing important changes if they don’t set up the MR correctly.

Impact

This inefficiency slows down release cycles, increases the risk of bugs slipping through, and wastes 5+ hours per week per engineer. For teams releasing weekly or monthly, the cumulative time lost adds up to hundreds of hours annually, directly impacting productivity and revenue-generating workflows.

Urgency

Teams cannot ignore this because it directly blocks their ability to review and validate release changes efficiently. Without automation, they risk human error in manual setups, which can lead to broken builds or missed critical updates. The problem becomes more urgent as release frequency increases.

Target Audience

This affects all GitLab users who rely on semantic versioning and tag-based releases, including DevOps engineers, software maintainers, and teams at mid-size to large tech companies. It’s particularly relevant for open-source projects, internal tooling teams, and companies with CI/CD pipelines where release validation is critical.

Solution Approach

A micro-SaaS tool that automatically creates merge requests (MRs) in GitLab when a new tag is pushed, comparing the code differences between the new tag and the previous major release. The tool integrates with GitLab via webhooks, detects tag pushes, and generates a dedicated MR showing the diff between versions—no manual setup required after initial configuration.

Key Features

3. is pushed, the tool automatically creates a branch and MR comparing it to the last major release (e.g., v
6. .
7. Release Diff Viewer: The MR includes a clean, side-by-side code diff, making it easy to spot changes without digging through commit logs.
8. Slack/Teams Notifications: Optional alerts to notify the team when a new release diff MR is ready for review.
9. Customizable Rules: Users can define which tags trigger MRs (e.g., only major versions like vX.
11. .

User Experience

Users install the tool via GitLab webhook, configure their tag rules (e.g., 'Create MR for tags matching v*.0.0'), and forget about it. Every time they push a new major tag, they receive a notification with a link to the pre-created MR showing all code changes. They can then review, approve, or comment on the diff—all within GitLab’s familiar interface.

Differentiation

Unlike manual workarounds or generic GitLab integrations, this tool is purpose-built for tag-based release diffs. It eliminates the need for manual branch/MR setup and provides a dedicated view for release comparisons, which GitLab’s native features don’t offer. The tool also reduces errors by automating the process, ensuring consistency across releases.

Scalability

The product scales with the user’s team size and release frequency. Teams can add more seats for additional users, and the tool supports unlimited repositories. Advanced features like Jira integration or custom diff viewers can be added as upsells for larger teams.

Expected Impact

Teams save 5+ hours per week per engineer by eliminating manual MR setup and change log reviews. They gain confidence in their releases by having a clear, automated way to validate changes. For businesses, this translates to faster release cycles, fewer bugs, and higher productivity—directly impacting revenue and operational efficiency.