Make action releases follow datadog-ci semver#55
Merged
juan-fernandez merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
daniel-mohedano
approved these changes
Apr 27, 2026
juan-fernandez
deleted the
juan-fernandez/release-bump-follows-datadog-ci
branch
juan-fernandez
added
the
semver-patch
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.
Summary
Follow up from #54
scripts/release-datadog-ci-bump.shchoose the action version bump from the pinneddatadog-cichange.v5to the first pinnedv5.x.yas an action minor bump.datadog-cisemver after that:datadog-ciminor bump => action minor bumpdatadog-cipatch bump => action patch bumpRELEASE.mdto document the release-versioning policy.Why
With the current script, the merged
#54bump would releasev3.0.1even though it is the first time the action moves from a floating default (v5) to an exact pinneddatadog-civersion. We want that transition to cutv3.1.0, and after that we want action releases to mirror the shape of thedatadog-ciupdate.Behavior
For the current repository state, the updated dry run now reports:
v3.0.0v3.1.0minordatadog-civersion:v5datadog-civersion:v5.14.0This PR should not carry the
datadog-ci-version-bumplabel. That label should stay on#54, since#54is the PR whose merge commit should be released.