Repository navigation
Release: start the macOS and Flatpak builds after publishing - #9
Merged
Merged
Conversation
The 2.2.0 release was published by release.yml's GITHUB_TOKEN, and GitHub does not let such an event start other workflows, so release-macos.yml and release-flatpak.yml never ran on `release: published` (they were started by hand). The publish job now dispatches both for the tag it published (actions: write; no secrets), and the workflow test checks it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Published October 17, 2026 from 444e75f: all 15 gates on both targets, signing, publication and the APT repository. The macOS images and the Flatpak bundles were attached by their workflows, started by hand for this release; the release notes for the process are updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
2.2.0 showed that a release published by
release.yml(withGITHUB_TOKEN) does not triggerrelease: publishedin other workflows, so the macOS images and Flatpak bundles were not built automatically; I dispatched them by hand for v2.2.0.gh workflow run release-macos.ymlandrelease-flatpak.ymlfor the tag it published (actions: write, no secrets).scripts/test-native-release-signing.mjschecks the dispatch and permission.Takes effect from the next release (the workflow file is read from the tag).
🤖 Generated with Claude Code