theholeTo whomever thought it would be a good idea to set a fixed ui5 version in some custom apps: thank you. Now I have to check every single app (close to 50) whether they have a fixed, unsupported version. Then we have to remove this setting and test the given apps properly, because the devs tend to access attributes directly, which might have been fixed in the current version of ui5...
AprazethYou do have to admit, it does give job security?
Good luck though, this sounds like a game of running around fixing stuff as it breaks in the dark :(
@Aprazeth after going trough all of them (of course I needed access to several), there are luckily not many which are with a different version and none are affected by the upcoming end of life cycle.
Sounds like it was a bit of an ordeal, but, it wasn't that bad™.
I take it you also made some notes on which ones had version constraints etc. to avoid a repeat in the future?
@Aprazeth yeah. We just need to remove the diverging versions, so that the current one is being used. But we don't have to test until the end of the month, because no used version is being affected by end of life cycle
@Aprazeth What's a bit weird is that those are rather new apps. I would have expected that older apps would have some diverging versions.
@thehole
On a completely unrelated note, noticed how a lot of slop PR's/code tends to use older versions of software because that is what the models were "trained" (read; the copy/paste from StackOverflow and such) on?
Of course that isn't always the case but it is kind of odd the frequency I have seen it happen.
Odd...
Anyway, I am sure that is not the case here :)