Skip to content

Conversation

@lucian-tosa
Copy link
Contributor

Ticket

CLOUDP-313981

Description

Bump Cloud Manager version for MongoDB Agent container images for mms version v20250423.

Reviewer Checklist

Before merging this PR, verify the following:

  • the following tasks are passing in Evergreen:
    • release_agent task (variant: release_agent)
  • the cloud_manager was updated correctly
  • the cloud_manager_tools was updated correctly
@lucian-tosa lucian-tosa requested review from a team, SimonBaeumer and anandsyncs and removed request for a team April 23, 2025 14:15
@lucian-tosa lucian-tosa merged commit cbf4b40 into master Apr 23, 2025
24 of 27 checks passed
MaciejKaras pushed a commit that referenced this pull request Apr 27, 2025
…… (#4313) … images for MMS release branch v20250423 (#30) # Ticket [CLOUDP-313981](https://jira.mongodb.org/browse/CLOUDP-313981) # Description Bump Cloud Manager version for MongoDB Agent container images for mms version v20250423. # Reviewer Checklist Before merging this PR, verify the following: - [ ] the following tasks are passing in Evergreen: - `release_agent` task (variant: `release_agent`) - [ ] the `cloud_manager` was updated correctly - [ ] the `cloud_manager_tools` was updated correctly --------- Co-authored-by: mms-build-account <mms-admin+pullonly@10gen.com> Co-authored-by: Evergreen <kubernetes-hosted-team@mongodb.com> (cherry picked from commit cbf4b40) # Summary <!-- Enter your issue summary here.--> ## Proof of Work <!-- Enter your proof that it works here.--> ## Checklist - [ ] Have you linked a jira ticket and/or is the ticket in the title? - [ ] Have you checked whether your jira ticket required DOCSP changes? - [ ] Have you checked for release_note changes? ## Reminder (Please remove this when merging) - Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible - Our Short Guide for PRs: [Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0) - Remember the following Communication Standards - use comment prefixes for clarity: * **blocking**: Must be addressed before approval. * **follow-up**: Can be addressed in a later PR or ticket. * **q**: Clarifying question. * **nit**: Non-blocking suggestions. * **note**: Side-note, non-actionable. Example: Praise * --> no prefix is considered a question
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

6 participants