Repository navigation
fix(release): macOS build without SwiftPM, ext tester from a pure-Dart package - #1484
Merged
Merged
Conversation
…t package
The 0.4.19 Release run failed in two places, both new since 0.4.18 (the
Flutter pin moved from 3.41.6 to 3.47.1 and the tester jobs were added):
- Build macOS: Flutter 3.47's Swift Package Manager integration cannot
resolve the vendored refresh_rate plugin ('target refresh_rate is outside
the package root': Package.swift points at ../Classes). The app opts out
of SwiftPM, so macOS builds use CocoaPods as before.
- Build querya-ext-tester (4 platforms): 'dart compile' does not support
build hooks, and the app's graph has sqlite3 and objective_c. The tester
is pure Dart, so scripts/ci/build_ext_tester.sh compiles it from a
throwaway package that holds lib/core/extensions and depends on path.
This was referenced Oct 11, 2026
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.
Hotfix for the failed 0.4.19 Release run (https://github.com/QueryaHub/Querya-Desktop/actions/runs/38149049982). Cut from the commit the
0.4.19tag points at, sopubspec.yamlstill says0.4.19+2.What failed
Build Linux, Build Windows and the E2E tests passed. Five jobs failed, which skipped Publish GitHub Release, Publish APT + DNF and Publish AUR. Both causes are new since 0.4.18, which built with Flutter 3.41.6 and had no tester jobs:
Error: Xcode failed to resolve Swift Package Manager dependencies: target 'refresh_rate' in package 'refresh_rate' is outside the package root. Flutter 3.47 turns Swift Package Manager on, and the vendoredthird_party/refresh_rate/macos/refresh_rate/Package.swiftpoints its target at../Classes.'dart compile' does not support build hooks, use 'dart build' instead. Packages with build hooks: objective_c, sqlite3.Fix
pubspec.yaml:flutter: config: enable-swift-package-manager: false, so macOS builds use CocoaPods as before (the plugin has a podspec).scripts/ci/build_ext_tester.shandrelease.yml: the tester is pure Dart (its import closure islib/core/extensionsandpackage:path), so it is compiled from a throwaway package namedquerya_desktopthat holds only that directory and depends onpath; no build hooks in its graph. Thequerya-mcpbridge already works the same way.Checked
--helpprintsUsage: querya-ext-tester, and an empty directory fails withmanifest.json not found, which are the two things the workflow's smoke test greps for.After merging
The
0.4.19tag has no GitHub Release yet, so it can be moved to the fix commit and the Release workflow re-run (decision pending).mainthen needs merging back intodev.