Repository navigation
Merge main into dev after the 0.4.19 release - #1489
Merged
Merged
Conversation
Release 0.4.18
- pubspec 0.4.19+2 (as on main after the 0.4.18 bump), AUR pkgver 0.4.19 - CHANGELOG: [Unreleased] becomes [0.4.19] - 2026-10-11 with what was merged since the last update; a new [Unreleased] keeps the planned items - release checklist: 0.4.19 product smoke, versioning and docs steps - roadmap: 0.4.18 shipped, 0.4.19 is this cut - Flatpak metainfo: 0.4.19 release entry
chore(release): Querya Desktop 0.4.19
…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.
fix(release): macOS build without SwiftPM, ext tester from a pure-Dart package
…nored querya-ext-tester declared Future<int> main and returned 0 / 1 / 2, but Dart ignores the return value of main: every run exited 0, so CI could not fail on a broken extension and the release smoke test (an empty directory must exit 1) failed. The code is now assigned to exitCode.
fix(ext-tester): set the process exit code (main's return value is ignored)
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
2 participants
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.
GitFlow back-merge:
mainintodevafter the 0.4.19 release.Brings into
dev:CHANGELOG[0.4.19], checklist, roadmap, Flatpak metainfo entry, AURpkgver);scripts/ci/build_ext_tester.sh; fix(ext-tester): set the process exit code (main's return value is ignored) #1485:querya-ext-testersets its exit code);pubspec.yamlis0.4.22+5, the next development version).No conflicts. After this
devandmainhave the same history again, so the next release branch will not collide onpubspec.yaml.