kacerr/gatewayapi-certificates-operator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: close out the conventions and listener-name plans
Deploy to K8s / deploy (push) Successful in 14s
Details

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
kacerr
2026-10-08 20:47:53 +02:00
co-authored by Claude Opus 5.5
parent 42b53b7538
commit 5c4a148b36
2 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans-executions/2026-10-08-2028-house-conventions.md
+4 -3
View File
@@ -9,7 +9,7 @@ Plan: `docs/plans/2026-10-08-2028-house-conventions.md`
- [x] Step 4 — Module path and version identity - [x] Step 4 — Module path and version identity
- [x] Step 5 — Baseline tests - [x] Step 5 — Baseline tests
- [x] Step 6 — CI build workflow - [x] Step 6 — CI build workflow
- [ ] Step 7 — Close out - [x] Step 7 — Close out
## Step 1 — CLAUDE.md ## Step 1 — CLAUDE.md
@@ -151,5 +151,6 @@ bugs deferred to the bug-fix phase, one test simplification declined.
Worth noting: the reviewer agents were not registered as agent types when the review Worth noting: the reviewer agents were not registered as agent types when the review
started (they were added in this session), so they were run as general-purpose started (they were added in this session), so they were run as general-purpose
agents told to follow the agent files. The `:latest` dispatch hole came in with the agents told to follow the agent files. The `:latest` dispatch hole came in with the
workflow copied from egress and is still open there. Step 7 stays unchecked until workflow copied from egress and is still open there. Pushed together with the listener-name fix
the branch is pushed and the MR is open. (`docs/plans/2026-10-08-2046-listener-name-sanitize.md`) as one MR. The CHANGELOG
entry is still owed, after the owner confirms it works.
docs/plans-executions/2026-10-08-2046-listener-name-sanitize.md
+8 -1
View File
@@ -6,7 +6,7 @@ Plan: `docs/plans/2026-10-08-2046-listener-name-sanitize.md`
- [x] Step 1 — Regression tests first - [x] Step 1 — Regression tests first
- [x] Step 2 — Fix - [x] Step 2 — Fix
- [x] Step 3 — Docs - [x] Step 3 — Docs
- [ ] Step 4 — Ship - [x] Step 4 — Ship
## Steps 1–3 — Tests, fix, docs ## Steps 1–3 — Tests, fix, docs
@@ -32,3 +32,10 @@ Deviations from the plan:
Worth noting: names that were valid before are unchanged, so existing listeners are Worth noting: names that were valid before are unchanged, so existing listeners are
not renamed. Not verified against a cluster; the production case is covered by the not renamed. Not verified against a cluster; the production case is covered by the
test using the exact cert and DNS name from the error log. test using the exact cert and DNS name from the error log.
## Step 4 — Ship
Pushed `feat/house-conventions` and opened one MR covering the conventions port and
this fix. Still owed after merge: tag `v0.1.0` with `/release`, restart the
deployment (it pins `:latest`), confirm the reconcile error is gone, then the
CHANGELOG entries.