Publishing a new package version does nothing?

[colinemondswieprecht]

Bug report

• [X] I confirm this is a bug with Supabase, not with my own application.
• [X] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When calling dbdev publish on an already-published package, I get a success message:
Published package uuidv7 upgrade from 1.0.1 to 1.0.2
I have previously done the same with an upgrade from 1.0.0 to 1.0.1, which was just a readme change. But the package version on database.dev is still 1.0.0.

To Reproduce

What I did, and I'm not going to reproduce it myself as I don't want to spam the server with broken test packages, especially since I can't delete them afterward:

1. Create a new package with a package--1.0.0.sql script.
2. Run dbdev publish.
3. Change something in the readme.
4. Run dbdev publish again.
5. Nothing happens. Find out from a different issue that that's the intended behavior.
6. Create a package--1.0.0--1.0.1.sql script that is empty.
7. Run dbdev publish again. There's a success message.
8. Check the package on https://database.dev. It's still 1.0.0.
9. Create a package--1.0.1--1.0.2.sql script that actually does something, hoping that that would change something (and actually also fixing a bug).
10. Run dbdev publish again, get a success message, nothing happens.
11. File a bug report.

Expected behavior

When I get the message Published package uuidv7 upgrade from 1.0.1 to 1.0.2, I expect database.dev to list that version.

System information

• OS: Windows
• dbdev: 0.1.6

Additional information

The current version of my control file:

# uuidv7 extension
comment = 'UUIDv7 extension'
default_version = '1.0.2'
relocatable = false
superuser = false

[colinemondswieprecht]

I just noticed that this bug has already been reported two months ago.

I will close this as a duplicate.