Update failed: repository changed its ‘Origin’ value from ‘whonix’ to ‘kicksecure’

When updating the workstation image today (QEMU/KVM image), I ran into the following problem:

Hit:1 tor+https://deb.whonix.org bookworm-developers InRelease                 
Hit:2 tor+https://fasttrack.debian.net/debian-fasttrack bookworm-fasttrack InRelease
Hit:3 tor+https://deb.debian.org/debian bookworm InRelease          
Hit:4 tor+https://fasttrack.debian.net/debian-fasttrack bookworm-backports-staging InRelease
Get:5 tor+https://deb.kicksecure.com bookworm-developers InRelease [62.0 kB]
Hit:6 tor+https://deb.debian.org/debian bookworm-updates InRelease
Hit:7 tor+https://deb.debian.org/debian-security bookworm-security InRelease
Hit:8 tor+https://deb.debian.org/debian bookworm-backports InRelease
Reading package lists... Done
E: Repository 'tor+https://deb.kicksecure.com bookworm-developers InRelease' changed its 'Origin' value from 'whonix' to 'kicksecure'
E: Repository 'tor+https://deb.kicksecure.com bookworm-developers InRelease' changed its 'Label' value from 'Whonix' to 'Kicksecure'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
terminal-wrapper-helper: [WARN]: Command exited with exit code '100'. You may close this window safely.

This is very similar to another thread, Qubes-Whonix update fails: repository changed its ‘Origin’ value from ‘whonix’ to ‘kicksecure’ (apologies, I can’t link it) – in which the solution appears to have required a repository fix. Is this the same problem resurfacing, or did I mess something up?

Thanks.

Should not use the developers repository.

Ah, crap. I completely forgot I did that. I meant to revert to the old snapshot and completely forgot. Thank you, and sorry to waste your time.