Closed strarsis closed 3 years ago
It's running, just broken 😞 We think it's due to this change: https://make.wordpress.org/core/2021/11/10/default-git-branch-for-wordpress-wordpress-develop/
Turns out it has nothing to do with the above ^ and was just an issue with GitHub actions (I think). We took this chance to simplify the workflow in https://github.com/roots/wordpress/pull/31.
In case this ever happens again, we'll just manually trigger this action.
@swalkinshaw: By the way: Is there a web hook that informs about new WordPress releases? Or some trick that listens on the WordPress SVN repositoryx?
GitHub RSS feed for releases: https://github.com/WordPress/WordPress/releases.atom
@swalkinshaw: Is this feed already used by this repository/cron
? Hadn't looked into all code yet.
You can't trigger a GitHub workflow from an RSS feed unfortunately. So this repo just has a workflow which runs every 10 minutes that checks for new tags and is idempotent https://github.com/roots/wordpress/blob/5eb33524cd08833d54b8d104b858bec3c2d78aa7/bin/update-wp-releases.php#L48-L54
Description
WordPress
5.8.2
was just advertised in the admin backend. But the tag isn't available in the repository yet (the tag for the previous release5.8.1
is). How often does thecron
run and check for new WordPress releases?Steps to reproduce
Expected behavior: Smaller
cron
intervals or a web hook/notification system for new official WordPress releases?Maybe add a trigger URL so a developer can trigger it manually (with rate limiting of course).
Actual behavior: Delay between new official WordPress release and available tag in repository.
Reproduces how often: It depends on when the new official release is published. When the
cron
happens to run right afterwards it may appear instantaneous.Versions
(Not applicable)