# Trigger Deployments on Git Tags

DevFeed: [Trigger Deployments on Git Tags](<https://devfeed.tech/articles/trigger-deployments-on-git-tags-19033.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/trigger-deployments-on-git-tags/>)

Author: Michael Fallihee

Published: 2026-06-05T00:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [Git](<https://devfeed.tech/topics/git.md>), [releases](<https://devfeed.tech/topics/releases.md>), [ci](<https://devfeed.tech/topics/ci.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bitbucket](<https://devfeed.tech/tags/bitbucket.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [features](<https://devfeed.tech/tags/features.md>), [git](<https://devfeed.tech/tags/git.md>), [git-tags](<https://devfeed.tech/tags/git-tags.md>), [github](<https://devfeed.tech/tags/github.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [product](<https://devfeed.tech/tags/product.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

## AI overview

Pulumi Deployments can now trigger stack deployments when matching Git tags are pushed. Teams can enable tag-based triggers, configure glob filters, and use the tag name in deployment commands or Pulumi programs. The feature works with GitHub, GitLab, Bitbucket, Azure DevOps, and Custom VCS integrations.

## Source excerpt

A git tag is how many teams mark a release as ready. Pulumi Deployments can now act on that signal directly: configure a tag-based trigger, push a version tag like v1.2.0, and Pulumi automatically runs pulumi up for your stack. No extra pipeline glue, no manual click -- your release tag is the deployment. Why tags? Push to Deploy has long let you preview changes on a pull request and update a stack when commits merge to a branch. That branch-based model is a great fit for continuous delivery to shared development and QA environments, where every merge should flow straight through. But promotion to production is often deliberate, not continuous. You merge throughout the day, then decide -- separately -- that a particular commit is the release. The conventional way to record that decision is a git tag: v1.2.0, 2026.06.0, release-2026-06-04. Tagging is already part of most teams' release rituals. Tag-based triggers connect that ritual to your infrastructure. Instead of wiring up a separate CI job to call the Pulumi Deployments REST API on a tag event, you configure the trigger once in your stack's deployment settings and let Pulumi handle the rest. How it works Tag triggers are controlled by two settings on your stack's deployment configuration: Run updates for pushed tags -- a toggle that enables running pulumi up when a matching tag is pushed. Tag filters -- a list of glob patterns that decide which tag names qualify. Tag filters use the same model as the path filters you may already know, except the patterns match against the tag name rather than changed file paths. A few examples: v* -- deploy on any tag beginning with v, such as v1.0.0 and v2.3.1. v* plus !*-rc* -- deploy on release tags but skip release candidates like v1.2.0-rc1. 2026.* -- deploy on calendar-versioned releases such as 2026.06.0. Filters prefixed with ! are exclusions, and an exclusion always wins over an include. With no filters configured and the toggle on, every tag push deploys. Deleting a tag never