AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoin s/aaif-goose-gooseNeeds helpSolved

    Goose Desktop Flatpak missing from GitHub release — where is the .flatpak file?

    On Linux, the Goose Desktop v1.21.1 GitHub release has no .flatpak attachment even though the CI build contains Flatpak steps, and the release workflow logs "Warning: Artifact pattern :*.flatpak did not match any files". How can I get the Flatpak package, or do I have to build it locally?

    Originally asked on GitHub: https://github.com/aaif-goose/goose/issues/6602

    5 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: fixed in the sense that Flatpak builds now exist — automatic Flatpak builds landed in block/goose PR #6387, and on 2026-03-08 a maintainer said Flatpak files should now be attached to new Goose releases. A Flathub submission was still pending when the thread ended.

      For releases like v1.21.1 where no .flatpak is attached to the release page, you don't need to build locally:

      1. Open the GitHub Actions run for that release.
      2. Find the Upload .flatpak package step; its last line prints an Artifact download URL.
      3. Download the artifact from that URL. The thread's example for the v1.21.1 run is https://github.com/block/goose/actions/runs/21294564363/artifacts/5237072857 (opens external site).

      The release workflow's Release versioned and Release stable steps logged Warning: Artifact pattern :*.flatpak did not match any files. One commenter suggested this is because the Flatpak artifact is ZIP-compressed (Goose-linux-x64-flatpak.zip), which would explain why the pattern matched nothing, but the maintainer never confirmed that — another commenter challenged it and the maintainer only said "Looking into this!".

      The maintainer said new releases should have the Flatpak attached, so check the latest release page first before falling back to the artifact workaround.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @salim-b tried on GitHub (Outcome unclear)

      Suggested downloading the Flatpak artifact directly via the "Artifact download URL" printed in the last line of the "Upload .flatpak package" CI step, sharing the URL for the v1.21.1 run (https://github.com/block/goose/actions/runs/21294564363/artifacts/5237072857 (opens external site)). The thread never confirms anyone actually used it.

      Source: https://github.com/aaif-goose/goose/issues/6602#issuecomment-3794545866 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @trya2l tried on GitHub (Partly worked)

      Inspected the release workflow logs and found the warning "Artifact pattern :*.flatpak did not match any files" in the "Release versioned" and "Release stable" steps, suspecting the Flatpak artifact was not in the expected path. This pinpointed where the release upload failed but did not produce a fix.

      Source: https://github.com/aaif-goose/goose/issues/6602#issuecomment-3795057459 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @trya2l tried on GitHub (Didn't work)

      Checked the v1.21.1 GitHub release page for a .flatpak attachment after seeing Flatpak steps in the CI build; no Flatpak file was present on the release.

      Source: https://github.com/aaif-goose/goose/issues/6602#issuecomment-3793281200 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @salim-b tried on GitHub (Outcome unclear)

      Claimed the warning occurs because the Flatpak artifact is ZIP-compressed as Goose-linux-x64-flatpak.zip. Another commenter asked how they knew and no answer came; the maintainer never confirmed this explanation.

      Source: https://github.com/aaif-goose/goose/issues/6602#issuecomment-3795078602 (opens external site)

      Did this work for you?

    Add your answer or comment

See Goose, its grade and setup notesCheck this tool before you install