feat: enhance release workflow with manual trigger and version bump o…#808
Merged
feat: enhance release workflow with manual trigger and version bump o…#808
Conversation
added 2 commits
February 13, 2026 14:20
…ptions Added a workflow_dispatch event to allow manual triggering of the release process with customizable tag version and bump type inputs. Updated deployment logic to handle tag versioning based on the create-release job output.
Contributor
Branch preview✅ Deployed successfully in branch deployment: |
Introduced a step to resolve the release tag before deployment, ensuring that an empty tag triggers an error to prevent destructive S3 sync. Updated the S3 bucket and version tag references to use the resolved tag value.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
…workflow Updated the deployment workflow to use the environment variable RELEASE_TAG for resolving the release tag, ensuring consistency and clarity in the tag resolution process.
yagopv
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
How it works
The workflow now supports two trigger paths:
Manual dispatch (new): Actions tab → "Release" → "Run workflow"
Release event (existing): Creating a release through the GitHub UI still triggers deployment as before — no change to the current flow.
Changelog
Checklist
safe-docspull request rulesNote
Medium Risk
Changes the production release/deploy pipeline and S3 destination selection; misconfiguration of inputs/permissions could impact what gets deployed, though the tag-empty guard reduces the worst failure mode.
Overview
Adds a
workflow_dispatchtrigger to the Release workflow so releases can be started from the Actions UI with optionaltag_versionor semverbump_type.Introduces a
create-releasereusable-workflow job gated toRELEASE_USERS, and wires thedeployjob to depend on it (while still supporting the existingrelease.publishedtrigger). Deployment now resolves the tag from either the created release output or the release event, fails fast if empty to avoid destructive S3 sync, and uses the resolved tag for the S3 path andVERSION_TAG.Written by Cursor Bugbot for commit 170c37b. This will update automatically on new commits. Configure here.