Hey @hansontools - thanks for reaching out. My guess is that you just need to refresh the page, as you shouldn't be seeing that message if the v0.1.9 release was already published. That does seem to be a reproducible bug, though. I'll document it internally and let you know when it's been fixed.
Furthermore, if in this state you try to use the "Latest version" button, it doesn't load the newest version in a new tab (with ?_releaseVersion=latest in the URL), but rather the Published version (so, no version param in the URL).
Until you refresh the page, of courseβthen it works again.
Maybe an obvious side effect, but worth noting nonetheless.
Ah okay, that is unfortunately the same buggy behavior that others are describing. The new release is actually being created and published, but the UI gets out of sync. We're actively tracking this and will hopefully be able to share an update soon.