Repository navigation
fix(publish-flatpak): attach bundles to the calling repository's release - #356
Merged
Merged
Conversation
repo-name is the registry image path and index key. gtk-office-suite sets it per app (tuna-os/letters, tuna-os/tables, tuna-os/decks), so uploading the bundles with --repo repo-name targeted repositories that do not exist and the tag's Publish Flatpaks run failed (v2.1.0, run 30248959744). Upload to GITHUB_REPOSITORY, the repository whose tag triggered the release; for repos where repo-name equals the repository this changes nothing.
hanthor
added a commit
to tuna-os/gtk-office-suite
that referenced
this pull request
Nov 7, 2026
The pinned revision uploaded release bundles with --repo tuna-os/<app>, which does not exist; #356 uploads to the calling repository.
hanthor-hive-agent
Bot
added
author/human
hanthor
added a commit
to tuna-os/gtk-office-suite
that referenced
this pull request
Nov 7, 2026
…lish (#1893) * ci(release): draft releases, attach SDK-built /app tarballs, then publish autorelease.yml pushed a tag but never created a GitHub release, so the reusable workflow's bundle upload and anything reading releases/latest had nothing to work with. It now creates the release as a draft before dispatching the publish. publish-flatpak.yml builds each app's /app tree in the GNOME SDK (x86_64 and aarch64), attaches <app>-<arch>.tar.gz and its sha256 to the release, and publishes the draft once the Flatpaks are out. FlatPark repackages these tarballs; building them from the tag in CI keeps the published bytes matching the tag they are filed under. Part of #1862. * ci(release): pin the reusable publish workflow to tuna-os/.github#356 The pinned revision uploaded release bundles with --repo tuna-os/<app>, which does not exist; #356 uploads to the calling repository.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
release-bundlesjob uploaded with--repo ${{ inputs.repo-name }}.repo-nameis the registry image path and index key, and tuna-os/gtk-office-suite publishes three apps from one repository withrepo-name: tuna-os/{letters,tables,decks}. The upload therefore targeted repositories that do not exist, and the tag publish failed (v2.1.0, run 30248959744). It now uploads to$GITHUB_REPOSITORY. Callers whoserepo-nameequals their repository (Tavern, dualcut, finupdate) are unaffected.Part of tuna-os/gtk-office-suite#1862.