./release.sh is confused about what packages are NEW

i'm trying to update rust-sequoia-sop from 0.22.2 to 0.25

if i use ./release.sh sequoia-sop, i see:

ATTENTION: this upload introduces NEW binary packages not already in the Debian
archive, you will need to build a binary package out of it.

PLEASE THINK CAREFULLY BEFORE UPLOADING NEW VERSIONS WITH NEW BINARY PACKAGES,
AS SUCH UPLOADS CAN AFFECT ONGOING TRANSITIONS AND DELAY THEM SIGNIFICANTLY.

For your reference, this source package builds 9 binary package(s):
librust-sequoia-sop+cli-dev
librust-sequoia-sop+compression-bzip2-dev
librust-sequoia-sop+compression-deflate-dev
librust-sequoia-sop+compression-dev
librust-sequoia-sop+crypto-cng-dev
librust-sequoia-sop+crypto-nettle-dev
librust-sequoia-sop+default-dev
librust-sequoia-sop-dev
sqop

Of those, the following are NEW:
librust-sequoia-sop+default-dev
librust-sequoia-sop-dev

This is incorrect: all the librust-sequoia-sop… packages would be NEW, as 0.22.2 only built the sqop binary package.

I'm going to try to update the debian packaging so that 0.25 still only builds the sqop binary package, but i thought i'd report the confusion here.