Skip to content

Conversation

@louis-cqrl
Copy link
Contributor

What does this PR do? What is the motivation?

Update version of FIPS Proxy

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

@louis-cqrl louis-cqrl requested a review from a team as a code owner March 28, 2025 11:54
@github-actions
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@louis-cqrl
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Mar 31, 2025

View all feedbacks in Devflow UI.
2025-03-31 07:11:40 UTC ℹ️ Start processing command /merge


2025-03-31 07:11:44 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 17m (p90).


2025-03-31 07:27:29 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit b4af56a into master Mar 31, 2025
18 of 20 checks passed
@dd-mergequeue dd-mergequeue bot deleted the louis-cqrl/release-fips-proxy-1.1.9 branch March 31, 2025 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants