{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiazmp2r5xfvi4ogm3a3ajmso4qdzeig7ybqwq35fpm3iht7jriyva",
    "uri": "at://did:plc:yrn4rbgwenb6lfhhzjegbtnc/app.bsky.feed.post/3mj3nnvx4hd62"
  },
  "path": "/t/integrating-flathub-releases-with-my-release-pipeline/11973#post_1",
  "publishedAt": "2026-04-08T15:09:42.000Z",
  "site": "https://discourse.flathub.org",
  "textContent": "I have a release pipeline with multiple jobs releasing to e.g. Github Releases, AUR, or NPM.\n\nNow I would like to integrate Flathub with the same pipeline. The manual process goes like this:\n\n  * I push a tag, and build a new release\n  * Then I manually update my Flathub repo with the new version and hash\n  * I push to a branch, and open a PR\n  * I wait ~10-15 minutes for the build to finish\n  * I merge the PR manually\n\n\n\nI can automate all of it up to the point where I wait for the PR build. How do you guys handle it and are there any recommended ways of handling that? I can’t think of anything better than a job that runs every 5 minutes and polls the repo for open PRs to merge, but obviously that’s ugly.\n\nA major roadblock is that Github won’t let you receive webhooks from a repo you don’t have admin access to, so a true event-driven pipeline is off the table here.",
  "title": "Integrating Flathub releases with my release pipeline"
}