That option was removed from the config in !192 (merged)
In pmbootstrap commit 520f34a253b6dc3dec1c0a7cba0880046d013fdb (~ September 2018) the CI still ran ./pmbootstrap.py kconfig check but it disappeared somewhere after that.
I didn't disable it on purpose. Looks like Purism's defconfig was changed to disable it.
Given that this device is still under heavy development, I would rather use the exact defconfig that purism is releasing in their kernel, rather than have to merge their changes with ours (e.g. to re-enable DM_CRYPT).
I know the goal is to have disk encryption on all the devices, but this isn't really a production device, and it would make moving to newer kernels/defconfigs easier if we didn't have to patch it every time. I can file a ticket in Purism's bug tracker thing to see if they would re-enable it in the upstream defconfig. In the meantime, is it possible to have CI skip this test for certain (i.e. this) devices?
Thanks for the pointer, @GrantM11235! Do you want to make a MR, which simply copies the upstream config, and removes !pmb:kconfigcheck from the APKBUILD?