fix: harden release workflow and resolve PR #3 conflicts - #4
Merged
Conversation
- Add GitHub Actions workflow for multi-platform builds and releases (Windows, macOS, Linux, Android, iOS, Web) - Add PowerShell setup script for Windows development environment initialization - Add VS Code configuration files for Dart/Flutter development - Rewrite README with comprehensive quick start guide, platform notes, and release procedures - Update dependencies (meta 1.17.0 → 1.18.0, test_api 0.7.10 → 0.7.11) - Remove sqlite3 system source configuration from pubspec.yaml to use precompiled binary
Improve GitHub Actions release workflow: include workflow name in concurrency group and only cancel in-progress runs for pull_request events; skip full platform builds (android/windows/linux/macos/ios) during pull_request runs. Add robust tag verification using gh CLI to ensure a remote tag exists and resolves to the exact commit targeted by the workflow (fail if mismatched) before uploading release assets. Other edits: remove hardcoded dart.flutterSdkPath from .vscode settings, clarify Flutter SDK path and CI-fixed version in README, and adjust setup.ps1 log text for Drift code generation. These changes prevent accidental release-asset overwrites and make local SDK config guidance clearer.
Merge main into the release-workflow branch, combine the trilingual README with onboarding/CI docs, gate the web build behind ENABLE_WEB_BUILD until unconditional dart:io imports are fixed, and treat any hyphenated semver tag as a prerelease. Co-authored-by: ALPACA LI <liyuanstudio273@gmail.com>
Existing prefer_interpolation / avoid_print / use_build_context_synchronously infos were failing `flutter analyze` and blocking the new release workflow. Co-authored-by: ALPACA LI <liyuanstudio273@gmail.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
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.
Summary
maininto the release-workflow changes and resolved the README conflict with the trilingual docs.ENABLE_WEB_BUILDuntil unconditionaldart:ioimports are fixed.flutter analyze --no-fatal-infosso pre-existing info-level lints do not block CI.Review notes
Same tip as updated #3. Prefer merging one of them after CI is green; close the other as duplicate.
Testing
release.ymlYAML syntax.