On Thu, 2026-08-20 at 14:02 -0500, Aaron Rainbolt wrote:
> On Thu, Aug 20, 2026 at 1:43 PM Adam Williamson
> <[email protected]> wrote:
> > 
> > Once again, I'm on a round of "branching happened and all these things
> > that have static lists of Fedora releases didn't notice".
> > 
> > Exhibit A: https://gitlab.com/fedora/bootc/base-images/-/work_items/83
> > Exhibit B: https://github.com/coreos/fedora-coreos-tracker/issues/2210
> > Exhibit C: 
> > https://gitlab.com/fedora/bootc/base-images/-/blob/main/RELEASE.md#part-3-managing-fedora-versions-in-konflux
> > 
> > yes these all happen to be bootc/coreos-related, but there are plenty
> > of offenders, that's just where I'm looking today.
> > 
> > The Fedora release cycle moves quite fast. Something important happens
> > approximately every two months: a release branches, or goes stable, or
> > goes EOL. You are not going to reliably keep up with this manually, and
> > you should not be trying.
> > 
> > There are two fairly solid ways you can check on what releases exist
> > and what state they're in:
> > 
> > 1. https://bodhi.fedoraproject.org/releases
> > 2. https://fedorapeople.org/groups/qa/metadata/release.json
> 
> The fact that both of these services are gated behind Anubis is not
> going to help automated tooling access them at all...

Properly-formed requests bypass anubis. (Apply in a less-likely-to-be-
scraped-location for details, or look at existing codebases that use
these endpoints).
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected]
https://www.happyassassin.net



-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to