dev-null

But if you haven't run armbian-install to actually install the new boot loader, it is only sitting there waiting to be installed.  Armbian does not automatically install new versions of the boot loader when apt pulls the new package, that is a manual step
Edit: I should have read all the posts as I see Werner already said this

This may be an issue. I know from the past Armbian and petitboot don't work well together. You need to wipe your spi to get rid of it. Then everything should work just fine.
 
Having this package installed means nothing about the actual used boot loader.
This package only provides the binaries to rewrite the boot loader if actually necessary. It is updated with package install/upgrade because doing so is rarely necessary. armbian-install can update the boot loader and will use the binaries from the package.

We've added some enhancements to our mirror redirect tool the allow you to choose a region.   
 
UPDATE: See Friendlier Documentation Here

The following regions are configured:
NA - North America
EU - Europe
AS - Asia (currently only china)
 
to use update the url in /etc/apt/sources.list.d/armbian.list from apt.armbian.com to apt.armbian.com/region/REGIONCODE
 
ex:
 
# cat /etc/apt/sources.list.d/armbian.list deb http://apt.armbian.com/region/NA focal main focal-utils focal-desktop  
If you'd like to choose a specifc mirror you can query https://apt.armbian.com/mirrors and find a mirror

FT232R, CH340 or CP2104 are known to work nicely. Search for any usb uart adapter built around one of these.
Don't get  CP2102 because if you ever get a rockchip board it would be useless.

Can confirm I'm also seeing this. I'm able to recover by installing the 23.02.2 linux-image-current-meson64 and linux-dtb-current-meson64 packages from /var/cache/apt/archives.
 
From what I can tell it's installing the modules for 6.1.50 in  /lib/modules but is somehow still booting 6.1.11
 
/boot/uImage isn't getting updated
$ strings /boot/uImage | grep "Linux version" Linux version 6.1.11-meson64 (root@29682b33de96) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #23.02.2 SMP PREEMPT Linux version 6.1.11-meson64 (root@29682b33de96) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #23.02.2 SMP PREEMPT Sat Feb 18 00:07:55 UTC 2023  
 
I can confirm that running the following command manually gets the device back into a working state
$ mkimage -A arm64 -O linux -T kernel -C none -a 0x1080000 -e 0x1080000 -n Linux -d /boot/vmlinuz-6.1.50-current-meson64 /boot/uImage