Enforce the format of tags for releases#3
Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit intomainfrom Feb 20, 2026
Merged
Conversation
Two tag formats are recognized: - vX.Y.Z -- for releases (where X, Y, Z are numbers) - vX.Y.Z-A -- for pre-releases (where X, Y, Z are numbers and A is anything) Goreleaser is configured to mark as prerelease when the second format is used.
|
✅ dbt Impact Preview dbt Impact Preview (placeholder) This is a test comment from the dbt-cicd provider. This comment will be updated automatically if new data arrives.🔗 Commit SHA: 0419d29 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
This comment has been minimized.
This comment has been minimized.
valeryjuli
approved these changes
Feb 20, 2026
gh-worker-dd-devflow-36fce6
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
gh-worker-dd-mergequeue-cf854d
bot
deleted the
jacobotb/K9VULN-10855/enforce-tag-version-format
branch
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
2 participants
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.
Motivation
Currently, the release workflow will run on any tag. We want to, at the very least, enforce the format of tags as version numbers.
Changes
Changed the workflow to recognize two patterns and goreleaser to generate prerelease or final releases depending on the format.
Two tag formats are recognized:
vX.Y.Z-- for releases (whereX,Y,Zare numbers)vX.Y.Z-A-- for pre-releases (whereX,Y,Zare numbers andAis anything)Goreleaser is configured to mark as prerelease when the second format is used.
Author Checklist
QA Instruction
This PR was used to generate a release named
v0.0.3-pre.1, which appears as a draft prerelease.Blast Radius
What services will this change impact. Is it only DataDog IaC Scanner, internal services, the documentation or anything else?
Additional Notes
If you need to share anything else along with your PR, please do it here.
I submit this contribution under the Apache-2.0 license.