|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #78140 List available releases as Feed (
Submitted: 2019-06-11 09:14 UTC Modified: 2021-08-04 12:55 UTC
From: arueckauer at gmail dot com Assigned: cmb (profile)
Status: Closed Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
 [2019-06-11 09:14 UTC] arueckauer at gmail dot com
This feature requests is releated to only ( has this feature already implemented). currently offers no other way of listing available releases, archives and latest versions other than the "directory listing" HTML (see

It would be a great feature to have a XML feeds (like, JSON or possible other formats.

As recommended by Anatol Belski (@weltling) (see I am opening this ticket for discussion. I would be happy to help on the implementation, but have no experience so far pertaining to the PHP website itself.


Add a Patch

Pull Requests

Pull requests:

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-06-11 12:52 UTC]
I don't think that having a separate news feed for the Windows
binaries/packages is appropriate, since these are just builds of
the source packages announced in the release news feed.
Instead we could add one (or multiple) links to the
release news feed pointing to the Windows builds (which would
require to have permanent links, though, i.e. we should no longer
move files to archives/ if new releases are available).

A file with machine readable information regarding available
releases/snaps etc. would make sense, though.  Allowing access to[1] might be a start.

[1] <>
 [2019-06-11 14:32 UTC] arueckauer at gmail dot com
Since downloads are offered on two different domains, I suggested a separate feed. However, adding to the news feed is fine with me, if that causes no other issues and the various windows versions (x86/x64, TS/NTS) are somehow detectable.
 [2019-06-13 20:33 UTC]
@cmb it's not about a news feed, i think. There's no request to issue separate release announcements or alike. It's merely about making the listings machine readable. That could be done by generating some JSON, similar how it is already done for snapshots, but including also archive releases. There might be a separate implementation for this as a cronjob, similar what is done for the snaps. We should not change the folder structure there, as it will sure break some users.

It is sure a chunk of work, but it would be sure useful for everyone and @arueckauer was willing to contribute it. We should just figure out what exactly were to do. Imo adding to the feed would be not very useful, as the information will need to be maintained twice at different places. For PECL, it already needs to be maintained at two places, but there's no good choice there. It is easier to integrate it on somehow, so it generates some releases.json. If we wanted, that could be also extended to the pecl releases.

 [2019-08-06 16:39 UTC] arueckauer at gmail dot com
Is there any way I can contribute to a solution on this issue?
 [2019-08-06 17:10 UTC]
> Is there any way I can contribute to a solution on this issue?

Yes, sure; that would be very welcome!

The source code of is publicly available[1], and
although it requires quite some tweaks to be run locally, you may
be able to provide a PR[2] which also would provide a better
discussion environment than this bug tracker. :)

[1] <;a=summary>
[2] <>
 [2019-08-19 11:34 UTC] Dnbsncbd dot 89 at icloud dot com
The following pull request has been associated:

Patch Name: protect master branches except for the pecl repos against force pushes
On GitHub:
 [2021-08-04 12:55 UTC]
-Status: Open +Status: Closed -Assigned To: +Assigned To: cmb
 [2021-08-04 12:55 UTC]
This has been resolved quite some time ago; there are now
release.json files available, e.g.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Feb 22 05:01:28 2024 UTC