More of a feature request, I guess.
The way we’re set up is that the Epic Launcher version v5.3.0 Engine+code was grabbed and distributed to our developers. However, nobody pulled down the debug symbols at the time. Now, they’re no longer available via the Epic launcher since v5.3.2 is latest, so I can’t grab them anymore.
I know we can grab the source from gitlab and build from there. However that then places me at a different version from our other developers.
I can understand not wanting to make old non-patched engine+source available. However, we’re locked to particular versions during production, and having the ability to retrieve previously published PDBs would be really useful.
Epic “tends” to do versioning such that the second decimal (#.#.X…) is optimizations, addressing stability, and bug fixes.
sometimes there are deprecation steps taken at these points, but that would only be for major issues. typically it is “safe” to perform these mid version updates, though if you were depending on the side effect from a “bug” to get a desired effect; then you might have issues.
if you have a concern then maybe on one of your dev systems create a directory image of the engine install location, do the update, and see if anything was relying on one of these side effects (if everything is broken or unrecoverable then you can revert the image). you might even be able to get the debug symbols at that point and then use those on the 5.3.0 systems with little issue.
there might be a greater cause for alarm for say going to 5.4+ as those changes can do full feature add/change/removal, or deprecation.