[CLOUDP-361632] Add functionality to upload release info to GitHub release assets

[viveksinghggits]

Summary

As discussed in the base PR, customers have been asking us to provide some details that can be used to figure out the container images that they need to deploy a specific version of MCK and MongoDB instance.
This PR does that. It add the functionality to add a new file called release_info_<release-version>.json to the GitHub release assets that would contain the details about MCK released images, OM, Agent, Search and the mapping between OM and agent's latest versions.

This is how the file loos like

https://gist.github.com/viveksinghggits/560e6179a3c7d9b11b0df68f02b15ccc

Proof of Work

Run the patch manually

evergreen patch --path .evergreen.yml -p mongodb-kubernetes -v add_releaseinfo_to_github_assets -t add_releaseinfo_to_github_assets -f -y -u --browse -d "Test add release info to github assets"

and make sure the new file is added to the release.

Screen.Recording.2025-12-02.at.23.00.35.mov

Screen.Recording.2025-12-02.at.23.08.27.mov

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 added changelog file? (will show up later)
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[viveksinghggits]

Hi @MaciejKaras , @nammn @mircea-cosbuc @vinilage ,
I had to re-open the PR that was already being reviewed here #623, the branch that was used in other PR was such that I was not able to push any new changes.
I have addressed the comment in this PR. can you please take a look again.

thank you, sorry for the confusion.

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.6.1 Release Notes

Bug Fixes

• Backed up the agent password in a secret for SCRAM authentication to prevent unnecessary password rotations.
• MongoDB Adding missing ownerrefs to ensure proper resource deletion by kubernetes.
• Single Cluster Deleting resources created by CRD now only happens on multi-cluster deployments. Single Cluster will solely rely on ownerrefs.
• MongoDB, MongoDBOpsManager: Improve validation for featureCompatibilityVersion field in MongoDB and MongoDBOpsManager spec.
  The field now enforces proper semantic versioning. Previously, invalid semver values could be accepted,
  potentially resulting in incorrect configurations.

Other Changes

• Future releases will include a new asset, release_info_.json, which provides detailed information about each MongoDB Controllers for Kubernetes release, including a clear list of all container images. This will help customers, especially those running in air-gapped environments, easily identify all required images for a given release.

[nammn]

you've changed repositories from a slice to a string.
The agents are released - as of right now - to 2 different repositories, how would we reflect that now?

[MaciejKaras]

Good question! The idea is to share information only about main repository. The other repository we push agent to mongodb-agent-ubi is used for backward compatibility issue. Related comment -> https://github.com/mongodb/mongodb-kubernetes/pull/624/files#r2597674694

[MaciejKaras]

Nice work! 🤩

[viveksinghggits]

@nammn when you get some time, can you please have another look into this.

[vinilage]

I left one comment proposing an improvement for the release notes.