3.8.1 release

Release Steps

Prep

• Confirm no further major MRs are incoming - patch release for zdu_start_point defaults to resources that don'... (#1155 - closed)

Backport Process (if applicable)

• Create support/<GET_major_minor_x> branch from GET tag
  • Example: For patch release 3.4.3, create support/3.4.x
  • Note: Branch must follow this naming convention to be protected
• Create MR to update GET version strings in repository
• Create MR targeting support/<GET_major_minor_x> with:
  • Cherry-picked commits for backporting
  • Cherry-picked commit for updated GET version

Release

• Update version strings in repository
  • ansible/galaxy.yml
• Confirm milestone exists
  • A milestone should typically already exist with all Issues and MRs attached
  • For patch releases, update cherry-picked Issues and MRs to point to the new milestone
• Create release notes
  • Follow similar style as previous releases
  • Reference commit history to collect all changes since last release
  • Format: Major items → Minor items → Upgrade notes/Breaking changes
  • Credit authors where appropriate
• Create the release
  • Select to create a new lightweight tag on the release page (no specific notes)
  • Add formatted release notes:
    • Format: Major items → Minor items → Upgrade notes/Breaking changes
    • Note any Terraform or Ansible dependency updates in the Upgrade Notes section
    • Credit authors where appropriate
    • Link to Docker and Terraform registries (same links as previous releases)
• Announce release in Slack channels:
  • #gitlab-environment-toolkit
  • #infrastructure_platforms
  • #g_dedicated_team
  • #support_self-managed

/cc @gitlab-org/software-delivery/get-maintainers