Release notes item

Team members for review and approval: Engineer(s): @engineers | Product Marketing: @PMM | Tech Writer: @eread | Product Designer(s): @ProductDesigners

Engineering Manager to merge when the feature is deployed and enabled: @nrosandich

Deprecations follow a different process.

Key dates

Timeline	DRI	Action
Monday of milestone week or earlier	PMs	Draft all release post item content and submit for review
Thursday of milestone week or earlier	TWs (required); PMM and PM Director/Group Manager (optional)	Complete reviews of release post item content
Friday of milestone week or earlier	TWs or EMs	Merge content by 00:00 UTC (midnight)

Note: Not all EMs have Maintainer role, so the EM needs to rely on the TW in this case. If necessary, make the MR dependent on the code MR.

Draft your content as soon as possible to avoid missing the cutoff!

Reminder: Make sure any feature flags have been enabled or removed!

PM release post item checklist

Expand for Details

Please only mark a section as completed after you perform all individual checks!

Set yourself as the Assignee.
Why? – The benefit of this feature to the user is clearly explained
Title:
- Length limit: 7 words (not including articles or prepositions).
- Sentence case.
Content:
- Make it clear whether the feature is new or an improvement to an existing feature.
- Ensure all links are functional and have meaningful text for SEO.
- Ensure that the text is fewer than 125 words.
Details block:
- Use the tiers, offerings, and status as detailed in the style guide.
- Ensure the documentation link points to the latest docs.
- Ensure all links to docs.gitlab.com content are relative URLs.
For any primary features:
- Be sure to include or revise the features.yml file as needed.
- A category is required, matching an entry in the categories.yml file.
- Update the pricing theme, if a Premium or Ultimate feature.
Add Reviewers: When the above are complete, add the Tech Writer, PMM, and Group Manager or Director as Reviewers.

Review

When the above checklist is complete and the content is ready for review, it must be reviewed by Tech Writing.

(Required) Tech Writer reviewed and approved
(Recommended) PMM reviewed and approved
(Optional) Product Designer reviewed and approved
(Optional) Group Manager or Director reviewed and approved

Any maintainer can merge. As soon as the code is in the branch, the release notes should be updated.

Agent notes

This MR was created by the release-notes-writer agent using --force mode. The following labels and metadata were inferred and applied (please confirm and update the source epic accordingly):

release post item::primary — inferred (notable Beta governance capability)
GitLab Ultimate — confirmed by PM
platform: GitLab.com, platform: self-managed, platform: dedicated — confirmed by PM ("all platforms")
devops::software supply chain security — confirmed by PM
group::compliance — confirmed by PM
Category: AI Governance — closest match from categories.yml (stage: software_supply_chain_security)

Outstanding items

⚠️ No documentation link — confirmed by PM that docs are not yet available. Engineering follow-up required before this MR is merged. The Links section in the release note currently only references the related epic.
⚠️ Confidential source epic — &20237 is currently marked confidential. Per the release notes guidelines, work item links in release notes must not be confidential. This epic must be made non-confidential before merging.
📋 features.yml and categories.yml — reminder to update features.yml in www-gitlab-com for this primary feature, and verify the AI Governance category in categories.yml is current.
📋 Pricing theme MR — required for primary Premium or Ultimate features.
📋 No image — per PM, no image is needed for this entry.

Edited Jun 25, 2026 by Isaac Durham

Add AI Audit Event Report (Beta) release note for 19.2