Until now products could declare multiple auto-update methods, but they all had to be of the same kind. For example if you used the git auto-update method, you could not use an additional github_releases or custom auto-update method. This is an issue as it prevents us to extend the auto-update process, for example by having a product using the 'git' auto-update method to retrieve all the versions, and a custom script to retrieve support and EOL dates. This improve the scripts execution orchestration to be able to support auto configurations using a mix of methods, meaning: - multiple kind of methods, such as git and github_release, - or multiple custom methods. A side-effect of those changes is that now a failure in a generic script does not cancel the update of subsequent products. Another side-effect, unwanted this time, is that now custom scripts managing multiple products, such as apple.py, are now executed multiple times instead of once.
18 lines
726 B
Python
18 lines
726 B
Python
import sys
|
|
|
|
from common import dates, endoflife, http, releasedata
|
|
|
|
METHOD = "npm"
|
|
|
|
p_filter = sys.argv[1] if len(sys.argv) > 1 else None
|
|
m_filter = sys.argv[2] if len(sys.argv) > 2 else None
|
|
for config in endoflife.list_configs(p_filter, METHOD, m_filter):
|
|
with releasedata.ProductData(config.product) as product_data:
|
|
data = http.fetch_url(f"https://registry.npmjs.org/{config.url}").json()
|
|
for version_str in data["versions"]:
|
|
version_match = config.first_match(version_str)
|
|
if version_match:
|
|
version = config.render(version_match)
|
|
date = dates.parse_datetime(data["time"][version_str])
|
|
product_data.declare_version(version, date)
|