Issue labels move to type/platform/area/status groups. Templates apply
the renamed type labels, the bug form gains HarmonyOS (reports such as
#308 had to pick Android), and questions are pointed at Discussions Q&A.
A workflow labels the platforms an issue mentions when it is opened.
Scanning title and body covers both form and free-form reports; on
existing issues it matched the form's platform in 46 of 55 and caught
reporters who picked the wrong dropdown entry.
Dependabot gets a fixed `dependencies` label so it no longer recreates
the ecosystem label `rust`.
The Windows release job built the bundles and then the portable binary,
so the portable link sat on the Canary critical path (56 min on
2026-10-08). Build the portable binaries in a separate matrix job; they
build their own frontend and, on Canary, restore the desktop release
cache of the same platform.
The repository cache was at its 10 GB limit and dev had lost every
desktop cache: Canary built from scratch (Windows 55 min cold against
36 min warm). The default rust-cache key ignored the matrix, so release
and debug builds on one runner shared a key. Give each Canary release
build its own key and leave the debug builds uncached. Stable and pull
requests no longer cache: caches saved under a tag or a PR ref are not
reused by later runs and only evicted dev's.
Validation: workflows parse; jobs, steps and publish dependencies
checked. Cache budget to confirm after the next Canary runs.
tauri.pilot.conf.json granted pilot:default inline, so it had to list
every capability file, and its list replaced the default set: a file
missing from it was silently off in pilot builds and the Windows and
macOS debug packages, as with desktop dialogs in 435f3f91. Move the
grant to capabilities/pilot/ and let build.rs load that directory only
when devtools-pilot is enabled. The feature is now the only switch;
drop the config file and its --config flags from the scripts and the
release workflows.
Validation: pnpm run check; the normal build embeds the five
capability files and the pilot build adds pilot-devtools; pilot eval
and assert in the macOS dev build.
* feat: add experimental OpenHarmony application build
* build(ohos): isolate experimental NAPI dependencies
* ci(ohos): build in this repository with public toolchain image
* ci: run existing checks for OHOS adaptation
* fix(ohos): generate QuickJS bindings for the OHOS target
* fix(ohos): use private caches and exclude desktop migration logs
* feat(ohos): restore native plugins and trusted endpoint confirmation
* ci(ohos): verify native plugin integration with existing checks
* chore(ohos): remove completed one-off validation workflow
* fix(ohos): clean dependency warnings and enable HAP LTO
* fix(ohos): retain shared plugin callbacks for the native bridge
* refactor(ohos): keep the native project and align the framework baseline
* fix(ohos): pin frame authorization and name the launcher entry
* fix(ohos): bind native builds and HAP packaging to the selected ABI
* fix(ohos): pin ordered Tauri bridge initialization
* fix(ohos): compress native libraries in HAP packages
* refactor(ohos): simplify HAP builds and Canary publishing
Build Rust once through the OHOS CLI and derive HAP versions from its merged
configuration. Replace the demo with the application page and remove generated
configuration writes, CMake scaffolding, and redundant preparation steps.
Keep ARM64 HAPs optional for Canary, report unsupported dev-log exports clearly,
and document the current build and host contracts.
Validated with pnpm run check, a local x86_64 HAP build and simulator smoke checks,
and Windows notification smoke checks.
---------
Co-authored-by: Darkatse <39111369+Darkatse@users.noreply.github.com>
Revert the armv7-android workaround added to avoid the ort-sys armv7 prebuilt gap: ORT was removed in 26ee3fdf, so armv7 can build again. Restores CC/AR env, rust target, bindgen sysroot, and build args for armv7-linux-androideabi while keeping the best-effort publish strategy.
Align the publish-side Linux repo package gate with the best-effort
strategy: if a partial run yields neither deb nor rpm artifacts, print
a skip notice and exit 0 instead of failing the publish job on
`test -ge 1`. Collector-level `--best-effort` already tolerates missing
desktop artifacts; this removes the leftover hard gate that prevented
publishing windows/mobile-only runs.
Allow the QuickJS feature release to publish whatever succeeded instead of requiring every platform to build: add --best-effort to the desktop asset collector, run desktop/mobile with continue-on-error, gate publish on prepare success rather than all jobs, and relax the Linux deb/rpm count check to at least one.
rquickjs-sys 0.9.0 ships no pregenerated bindings for android targets. Gate the bindgen feature behind target_os android so desktop keeps using bundled bindings without a libclang dependency. Mobile job installs llvm/libclang and exports BINDGEN_EXTRA_CLANG_ARGS pointing at the NDK sysroot.
pnpm/action-setup@v4 conflicts with the packageManager field in package.json (pnpm@10.34.5). Remove the explicit version so the action reads packageManager, matching the locally pinned pnpm.
- Replace per-push trigger with quickjs-build*/quickjs-release* tags, keeping workflow_dispatch for manual runs
- Add Android mobile job ported from canary-release, with NDK cross-clang env so rquickjs-sys can compile QuickJS C sources for Android targets
- Pass Android apk/aab artifacts through the publish step alongside the strictly validated desktop bundle set
Align the QuickJS feature branch release with the canary desktop pipeline:
- desktop-only matrix (win, mac x64/arm64, linux x64/arm64) with portable builds
- no signing / notarization, no apt/rpm repo publish, no nix, no Codex
- deterministic commit-based release notes
- move QuickJS-Feature tag via gh api PATCH (force) instead of git push
- fix missing linux-version step reference
- add desktop-only asset collector (scripts/ci/collect-desktop-release-assets.mjs)
- Create dedicated workflow for feature/quickjs-script-engine branch
- Automatically build and release on push to feature branch
- Use QuickJS-Feature tag for tracking releases
- Support manual trigger via workflow_dispatch
- Include multi-platform builds (Linux, Windows, macOS)
- Generate release notes with feature highlights
