CLOUDP-295785 - GitHub Actions workflow that checks for changelogs

[MaciejKaras]

Summary

This pull request introduces workflows to automate the validation and generation of release notes. It includes new script scripts/release/check_changelog.py for validating changelog file in PRs, created GitHub Actions workflow that calls validation script and another one to create release notes preview.

GitHub Actions Workflows

• Added .github/workflows/preview_release_notes.yml to generate and preview release notes for pull requests and pushes to master and release-* branches.
• Added .github/workflows/require_changelog.yml to validate the inclusion of changelog entries in pull requests. The requirement can be skipped by labelling PR with skip-changelog. Underneath the workflow uses scripts/release/check_changelog.py script.
• Introduced .github/actions/setup-ubuntu-host/action.yml to set up an Ubuntu runner with Python and necessary dependencies for workflows.
• Updated Pull Request template
• Updated CONTRIBUTING.md

Proof of Work

Changelog requirement validation

When changelog exists -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16319921866/attempts/1#summary-46094783625

Changelog entries found and validated

When changelog does not exist -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16322098714/attempts/1#summary-46102343972

No changelog entries found.
Exiting with error due to no changelog entries found.

When changelog does not exist and the skip-changelog label was added -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16322136466/attempts/1#summary-46102478174

No changelog entries found.

Release notes generation

Comment with Release Notes preview -> #263 (comment). GHA job summary -> https://github.com/mongodb/mongodb-kubernetes/actions/runs/16322098704/attempts/1#summary-46102343937

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
• 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

[m1kola]

LGTM in general. Blocking just so that we double check that we do not expose secrets to malicious PRs.

[github-actions]

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

MCK 1.3.0 Release Notes

Other Changes

• Optional permissions for PersistentVolumeClaim moved to a separate role. When managing the operator with Helm it is possible to disable permissions for PersistentVolumeClaim resources by setting operator.enablePVCResize value to false (true by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role.
• subresourceEnabled Helm value was removed. This setting used to be true by default and made it possible to exclude subresource permissions from the operator role by specifying false as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for this OpenShift issue. The issue has since been resolved and the setting is no longer needed.