GLPI CR reference now a required field (dev-only PRs declare no-CR). Standard: https://projects.knownelement.com/issues/820 Ticket: https://projects.knownelement.com/issues/811
22 lines
920 B
Markdown
22 lines
920 B
Markdown
## Release PR (dev -> release)
|
|
|
|
Merging this deploys to production (pfv-bms restarts if packages/** or
|
|
configuration.yaml changed).
|
|
|
|
### Change management (ruling 2026-09-06 — mandatory)
|
|
- GLPI CR deep link (required): https://cmdb.knownelement.com/front/change.form.php?id=N
|
|
- Dev-only PRs: state `no-CR (dev-only)` explicitly.
|
|
|
|
### Gate checklist (branch protection enforces the mechanical parts)
|
|
- [ ] CI green on the head commit (yamllint + secret scan + SDLC suite)
|
|
- [ ] CR filed in GLPI and referenced above (production changes)
|
|
- [ ] Adversarial pass done: what breaks if this is wrong? what watches for it?
|
|
- [ ] post-deploy validation (#778) will run on restart — expected entity changes noted below
|
|
|
|
### Reviewer (founder)
|
|
- [ ] Diff reviewed
|
|
- [ ] Approve to release
|
|
|
|
Expected entity/automation changes: <list or "none">
|
|
Rollback: git revert <sha> on dev, re-PR, or push previous release sha directly.
|