Skip to content

Commit 02bbd47

Browse files
committed
docs: mark the maintainer-change procedure as in progress, not complete
The change log claimed requirement 2 was satisfied by a review that has not happened yet. Record it as open until this change is actually reviewed and merged, so the entry describes a state someone can verify. Also extend the non-enforcement note to the approval requirement in the review and merge policy: without branch protection, neither is a gate.
1 parent dc3a4ad commit 02bbd47

1 file changed

Lines changed: 18 additions & 12 deletions

File tree

‎MAINTAINERS.md‎

Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -45,18 +45,24 @@ Adding or removing a maintainer requires:
4545

4646
### Change log
4747

48-
- 2026-07-27 — [@Wibias](https://github.com/Wibias) added as a maintainer at
49-
the project owner's request (requirement 1). Requirement 2, review by another
50-
current maintainer, is satisfied by the review on the pull request that lands
51-
this change; the entry is recorded here at merge time. Scope covers issue and
52-
pull-request triage, `dev` integration, and provider/CI maintenance.
53-
Security-boundary ownership in `.github/CODEOWNERS` is deliberately
54-
unchanged: authentication, credential handling, GitHub Actions, and release
55-
automation keep the two owners already listed for those paths, so this
56-
addition does not widen the review surface for them. Note that CODEOWNERS
57-
requests reviews rather than enforcing them — no branch protection rule is
58-
configured on this repository, so code-owner approval is a convention here,
59-
not a gate. Widening the boundary, or enforcing it, is a separate decision.
48+
- 2026-07-27 — [@Wibias](https://github.com/Wibias) added as a maintainer.
49+
Requirement 1 (agreement from the project owner) is met: the owner requested
50+
the addition. **Requirement 2 (review by another current maintainer) is still
51+
open** and is satisfied when this change is reviewed and merged; until then
52+
this entry records an in-progress change, not a completed procedure.
53+
Requirement 3 is met by this file and `.github/CODEOWNERS`.
54+
55+
Scope covers issue and pull-request triage, `dev` integration, and
56+
provider/CI maintenance. Security-boundary ownership in `.github/CODEOWNERS`
57+
is deliberately unchanged: authentication, credential handling, GitHub
58+
Actions, and release automation keep the two owners already listed for those
59+
paths, so this addition does not widen the review surface for them.
60+
61+
CODEOWNERS requests reviews rather than enforcing them — no branch protection
62+
rule is configured on this repository, so code-owner approval is a convention
63+
here, not a gate. The same is true of the approval requirement in the review
64+
and merge policy above. Widening the security boundary, or enforcing either
65+
of these through branch protection, is a separate decision.
6066

6167
## Security reports
6268

0 commit comments

Comments
 (0)