Skip to content

feat: enhance release workflow with manual trigger and version bump o…#808

Merged
eniayomi merged 6 commits intomainfrom
feat/automate-tag-creation
Feb 13, 2026
Merged

feat: enhance release workflow with manual trigger and version bump o…#808
eniayomi merged 6 commits intomainfrom
feat/automate-tag-creation

Conversation

@eniayomi
Copy link
Copy Markdown
Contributor

@eniayomi eniayomi commented Feb 13, 2026

Summary

  • Adds workflow_dispatch trigger to the existing release workflow, enabling production releases directly from the GitHub Actions UI
  • Integrates the create-release reusable workflow for tag creation with optional auto-generated semver bumps
  • Restricts who can trigger releases via the RELEASE_USERS repository variable

How it works

The workflow now supports two trigger paths:

Manual dispatch (new): Actions tab → "Release" → "Run workflow"

  1. Optionally provide a tag version or select a bump type (patch/minor/major) to auto-generate
  2. create-release job validates the actor against RELEASE_USERS, resolves the tag, and creates a GitHub release
  3. deploy job builds and deploys to production using the created tag

Release event (existing): Creating a release through the GitHub UI still triggers deployment as before — no change to the current flow.

Changelog

Checklist


Note

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_dispatch trigger to the Release workflow so releases can be started from the Actions UI with optional tag_version or semver bump_type.

Introduces a create-release reusable-workflow job gated to RELEASE_USERS, and wires the deploy job to depend on it (while still supporting the existing release.published trigger). 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 and VERSION_TAG.

Written by Cursor Bugbot for commit 170c37b. This will update automatically on new commits. Configure here.

Oluwapelumi Oluwaseyi 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.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 13, 2026

Branch preview

✅ Deployed successfully in branch deployment:

https://feat_automate_tag_creation--docs.review.5afe.dev

Comment thread .github/workflows/deploy-release.yml
Comment thread .github/workflows/deploy-release.yml Outdated
Comment thread .github/workflows/deploy-release.yml Outdated
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.
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread .github/workflows/deploy-release.yml Outdated
…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.
@eniayomi eniayomi merged commit bf9bad5 into main Feb 13, 2026
5 checks passed
@dasanra dasanra deleted the feat/automate-tag-creation branch March 10, 2026 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants