惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Microsoft Azure Blog
Microsoft Azure Blog
WordPress大学
WordPress大学
小众软件
小众软件
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
Hugging Face - Blog
Hugging Face - Blog
美团技术团队
博客园 - 三生石上(FineUI控件)
Last Week in AI
Last Week in AI
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - Franky
Microsoft Security Blog
Microsoft Security Blog
Y
Y Combinator Blog
A
About on SuperTechFans
The GitHub Blog
The GitHub Blog
U
Unit 42
H
Hackread – Cybersecurity News, Data Breaches, AI and More
云风的 BLOG
云风的 BLOG
IT之家
IT之家
MyScale Blog
MyScale Blog
V
Visual Studio Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
I
InfoQ
博客园 - 司徒正美

Flathub Status

GitHub is experiencing issues | Flathub Status Website is down | Flathub Status Multiple services down | Flathub Status Infrastructure provider outage | Flathub Status Publishing delay due to delta regeneration appstream2 branch referencing stale commit Signing outage | Flathub Status CDN cache invalidation issue | Flathub Status CDN cache invalidation issue | Flathub Status Website facing intermittent disruptions | Flathub Status Publish outage | Flathub Status Build service outage | Flathub Status Hosting provider planned maintenance | Flathub Status Blocked publishing due to ongoing repository pruning Frontend service is down | Flathub Status
Build status updates failing | Flathub Status
2026-05-08 · via Flathub Status

May 7, 2026 at 16:03 UTC

Build service

Resolved after 18h 47m May 8, 2026 at 10:50 UTC


GitHub pull request status updates, branch commit statuses, and flathubbot comments were failing due to a missing token in the build service configuration, despite builds being completed successfully. As a result, affected pull requests did not receive status updates or completion comments, and branch commit statuses were not being updated.

The issue has been resolved now, and all affected open pull requests should be updated with their build statuses. Some commit statuses may still remain outdated, but this does not affect the publishing process.

If any pull request completed successfully but still lacks a status update, please restart the build by commenting bot, build on the pull request. (10:50 UTC — May 8)