ci: open PR for post-release version bump instead of direct push#547
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Contributor
|
kaahos
approved these changes
May 27, 2026
Contributor
CI Test ResultsRun: #26508489831 | Commit:
Status Overview
Legend: ✅ passed | ❌ failed | ⚪ skipped | 🚫 cancelled Summary: Total: 32 | Passed: 31 | Failed: 0 | Cancelled: 1 Updated: 2026-05-27 14:33:16 UTC |
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.
What does this PR do?:
The release script tried to push the post-release version bump commit directly to
main, which is now blocked by the branch ruleset requiring all changes to go through a PR.Instead of pushing directly, the script now:
automated/bump-X-Y-Zbranch with the version bump commitmainMotivation:
Branch ruleset enforcement broke the
Validated Releaseworkflow — direct pushes tomainare no longer allowed. The bypass actor approach is locked down at org level, so a PR-based flow is the only path.Additional Notes:
The release itself (tag + release branch + GitLab trigger) is unblocked. The version bump PR is a required manual follow-up step.
How to test the change?:
Run the
Validated Releaseworkflow withdry_run: true— the bump path is skipped in dry-run so no PR is created. A real run will create the bump PR and print its URL in the job summary.For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance.Labels: AI