Fetch Java versions with their dates from https://www.java.com/releases/.
This script is using a new dependency: requests-html (https://requests-html.kennethreitz.org/). This is because https://www.java.com/releases/ needs JavaScript to render correctly. And for this to work requests-html automatically downloads Chromium because of its dependency to pyppeteer.
Chromium is downloaded into PYPPETEER_HOME, so the workflow has been modified to set this directory as a subdirectory of ~/.cache. Note that declaring the same environment variable from the python script does not work.
There were two issues with the macOS regexes:
- The regexex accepted only spaces separator. But non-breakable spaces are also used from time to time. Replacing spaces by \s fixed the issue (other product regexes were also updated - never know).
- The first regex, the one that accepted major releases with no minor version, were not useful (covered by the second regex) and partly catched valid versions (such as 13.1), who was then ignored. I removed it.
1. Drop RC and milestone releases by adopting a simple
version regex. Drops a few non-stable releases from
jreleaser and tomcat. Tested against all of the maven
automated pages
2. Fix pages with multiple auto: maven entries. In particular,
groovy was using this, but the newer 4.0 releases were not
being written correctly to disk.
Initial support for NPM Automation. This isn't widely used, since most NPM projects
will use git tags as well, but helpful for a few projects.
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
* Fix fstrings and remove unused imports
* Fix the merge of product config with default config in npm.py and pypi.py
If product config is first, default config overrides product config.
* Simplify npm.py
Co-authored-by: Nemo <me@captnemo.in>
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Co-authored-by: Marc Wrobel <marc.wrobel@gmail.com>
This avoids using the GKE APIs, much cleaner as a result.
The downside is that we need to keep track of all channels
separately. This also tracks the date a version is made available
on a channel, not the date it is made the default. This is being
slightly optimistic, but I think works well
