Hi Lauren,

Technically it is possible to create new versions that do not
introduce any changes. I do not know whether this is by design or not.
It is certainly not necessary to prevent it.

Is your design bug inquiry only about the asymmetry between "Changes"
and "Save", where the former has a special case for "no changes", but
the latter does not have it? Or did you expect something else to be
different or behave differently as well?

Kind regards,
Jakob

Am Sa., 30. Apr. 2022 um 04:38 Uhr schrieb Lauren Pullen <drurowin at gmail.com>:
>
> Hi Jakob,
>
> On 4/29/22 06:29, Jakob Reschke wrote:
> > Hi Lauren,
> >
> > I assume that your version was saved in the package cache directory, which
> > you can find in the list of repositories along with the remote repositories.
> >
> > If you find it there, you could use the "Copy" button to copy the version
> > to another repository, such as the inbox. This effectively tries again to
> > upload it.
> >
> > Or is the version listed in the remote repository but corrupt there?
> Actually, I think there might be a design bug.  Nothing is corrupt.  I
> just never noticed this happens before.
>
> Are you supposed to be able to Save a working copy that has no changes?
>  Like, when you ask the package for changes when there are none it says
> 'no changes' instead of bringing up a changes window with an empty list.
>