From 182e5548e23a84ebc52a7469779d39b3f262d0d2 Mon Sep 17 00:00:00 2001 From: Susana Ferreira Date: Tue, 7 Oct 2025 10:47:41 +0100 Subject: [PATCH] chore: update MAINTAINER.md to check PR version label (#460) ## Description Update MAINTAINER.md to include a check of the version label on the PRs ## Type of Change - [ ] New module - [ ] Bug fix - [ ] Feature/enhancement - [x] Documentation - [ ] Other --- MAINTAINER.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/MAINTAINER.md b/MAINTAINER.md index 7d80d2fa..d37ea26d 100644 --- a/MAINTAINER.md +++ b/MAINTAINER.md @@ -23,6 +23,7 @@ Check that PRs have: - [ ] Working tests (`terraform test`) - [ ] Formatted code (`bun run fmt`) - [ ] Avatar image for new namespaces (`avatar.png` or `avatar.svg` in `.images/`) +- [ ] Version label: `version:patch`, `version:minor`, or `version:major` ### Version Guidelines @@ -32,7 +33,8 @@ When reviewing PRs, ensure the version change follows semantic versioning: - **Minor** (1.2.3 → 1.3.0): New features, adding inputs - **Major** (1.2.3 → 2.0.0): Breaking changes (removing inputs, changing types) -PRs should clearly indicate the version change (e.g., `v1.2.3 → v1.2.4`). +PRs should clearly indicate the intended version change (e.g., `v1.2.3 → v1.2.4`) and include the appropriate label: `version:patch`, `version:minor`, or `version:major`. +The “Version Bump” CI uses this label to validate required updates (README version refs, etc.). ### Validate READMEs