Thanks for the clarity Hannes.  Here are some finer points to note about this:

  - This is nothing new, it's been this way forever.

  - It only affects when installing at the package level, not the
release level which is the normal use case.

  - If there is only one release for a particular Squeak version (the
usual case), then there is only one correct version to load, even
though the Warning is annoying and/or disruptive.

  - checking the 'published' box will make it so the Warning is not
displayed during the above conditions

I think we now have a clearer understanding of the potential use for
the "published" flag -- what you said Hannes -- for the case when
there is more than one release per Squeak release, although I suppose
it should probably pick the most recent then...   Hmm...
On Mon, Oct 8, 2018 at 3:18 PM H. Hirzel <hannes.hirzel at gmail.com> wrote:
>
> Hello
>
> The discussion about SqueakMap entries (see most recent email by Chris
> Muller)  has shown that the following is important:
>
>    You MUST check the 'published' flag in the entry.
>
> Otherwise the client code will load an older version thus not giving
> the users the release you intend them to give.
>
> Regards
> Hannes
>