gitlab-19.0 ai-code-review secrets-management multi-project-config ci-cd

GitLab 19.0 adds group-level review instructions, secrets manager

Group-level custom review instructions eliminate duplication across projects; GitLab Secrets Manager exits closed beta for Premium/Ultimate tiers, reducing external vault dependencies.

Summary

Developers managing multi-project teams now sync code review guidelines once instead of per-project; native secrets storage cuts operational overhead of maintaining separate HashiCorp Vault or AWS Secrets Manager instances.

Why it matters

Implementation verdict

Group-level instructions replace project-level duplication immediately via .gitlab/duo/mr-review-instructions.yaml cascading. Secrets Manager requires Premium/Ultimate tier and explicit opt-in per group/project; still in open beta (not production-ready per policy). Start with review instructions now; defer secrets to stable release or test in non-production first.

Sources

1.Group-level custom review instructions for GitLab Duo
2.you could only define custom review instructions for GitLab Duo at the project level. Teams working across many projects in the same group had to duplicate the same instructions in every project
3.GitLab Secrets Manager is now available in open beta for Premium and Ultimate customers on GitLab.com and GitLab Self-Managed
4.During open beta, GitLab Secrets Manager follows the beta support policy and might not be ready for production use
5.Most teams relied on external services such as HashiCorp Vault or AWS Secrets Manager

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs