frankblank
commented
4 years ago I also think that time has come to change the source to API instead of the deprecated json. We are still running some 6.2 / 7.6 and 8.7 instances
Open ghost opened 4 years ago
frankblank
commented
4 years ago I also think that time has come to change the source to API instead of the deprecated json. We are still running some 6.2 / 7.6 and 8.7 instances
Currently the legacy json feed is fetched fo releases.
https://get.typo3.org/json
Don't know since when, but the old json api isn't updated with elts releases which requires us to manually update the version requirement for a secure core test.
The new api https://get.typo3.org/v1/api/doc offers various methods to check, fo rexample for latest releases and for latest security releases in a given major version.
https://get.typo3.org/v1/api/major/7/release/latest https://get.typo3.org/v1/api/major/7/release/latest/security
Due to the new api, even elts is available as a flag so it would be possible to check for latestLTS and latestELTS (dunno if the case is required in realworld.. :)
Since this is available for all major versions, the cronjob for fetching core versions could be extended to select only the ones one would need (in our case we're only interested in 7 & 8).
Anyone interested besides me ? Would love to help, but would want to discuss it further to define what exactly, or maybe how exactly this should be implemented.