Impact of new builds

[hiran]

I agree. Since we do not have a monorepo, how can we make sure the "Source code (zip)" in future versions will contain what the one for v1.92 does?

According to AI "What IS included (in Source code (zip))

All tracked files: Every file and folder currently committed to the repository at that specific tag/commit.

The directory structure: The folder hierarchy is preserved exactly as it appears in your main or master branch.

License and README: These are included just like any other source file."

To make the move to a monorepo, we should [...]

I'm afraid I am not there yet. My worry is that by the next release of Oolite we forgot a manually added oolite-source.zip is required and we will start over this discussion.

Let's have the github workflow automatically create that file. AFAIK it is the repo content including submodules bar one file. Your AI agent neglected that part. Thus Github's automatically generated Source.zip will never deliver the required file.

I think now that I am scanning Flatpak and AppImage builds internally I am getting it. The version number inside the resources contains way less information with the new builds that it had in the builds before that.

What used to be something like 1.91.0.7749-250802-cf91fd5 is a simple 1.91 now.
What I expected to be something like 1.93.0.7775-260221-e400ac6 is a simple 1.93 now.

With that it is merely impossible for OoliteStarter to tell a user that a new (experimental) version is available. Why has it been removed?