aboutsummaryrefslogtreecommitdiff
path: root/tests/installer-steps/test_pacman_hook_order.py
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-20 07:27:16 -0500
committerCraig Jennings <c@cjennings.net>2026-07-20 07:27:16 -0500
commit2e062cc27285f79d75ce49f15a26ea8ebba9764f (patch)
tree46708b4e2e3c0c2b725be83b2f27828f157fbdb0 /tests/installer-steps/test_pacman_hook_order.py
parent0468fedb23ae34a140b6a5a903adedb4e9873ca5 (diff)
downloadarchsetup-2e062cc27285f79d75ce49f15a26ea8ebba9764f.tar.gz
archsetup-2e062cc27285f79d75ce49f15a26ea8ebba9764f.zip
docs: log overnight code audit and file triaged installer bugs
Overnight sentry ran its hygiene passes plus a code-inspection pass over the installer and the scripts/ directory. It archived 6 completed tasks to Resolved and logged 19 bugs and 12 refactors in docs/design/2026-07-19-sentry-code-findings.org. I filed the bugs as tasks graded by severity times frequency. Nothing in the codebase changed, this was detection only. Two things stand out. The installer does no partitioning (it's a post-install config layer), so the real data-loss surface is boot config, and it overwrites GRUB_CMDLINE wholesale, which can drop a cryptdevice or resume param and leave a machine unbootable. Three WireGuard configs with live private keys are tracked in git, flagged for a rotate-or-keep decision.
Diffstat (limited to 'tests/installer-steps/test_pacman_hook_order.py')
0 files changed, 0 insertions, 0 deletions