@wenathlan/devthink 2.0.12 → 2.0.14

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # DevThink release notes
 
+## 2.0.14 — the saddle workflow features answer the container product, the family surface completes
+
+### Changed
+
+| Area | Change |
+| --- | --- |
+| The four-architecture container index | The publish lane ships the family union surface the saddle publish lane established: linux/amd64, linux/arm64, linux/ppc64le and linux/s390x in one versioned index with provenance and sbom, the qemu setup pinning exactly the three emulated legs, the idempotent publish check comparing the four-arch sorted set, and the post-publish assertion fixing the published surface the same way. The runtime base gains its own arg — the trixie slim line is the only 26.8.x slim tag whose manifest still answers all four architectures (26.8.2 dropped s390x in every variant, an upstream build gap; bookworm never carried it), so the build stages keep the pinned toolchain line while the runtime rides the four-arch base, and the smoke-boot watchdog scales its budget for the ppc64le and s390x legs the same way the builder scales its test timeouts for the emulated arm64 (30 seconds native, 90 under qemu). |
+| The security lane at push time | The saddle security features the merge left behind ride the security workflow: the biome security gate (the isolated config that elevates the security rule group to blocking severity over the merged tree, with the family lockfile exclusions the integrity hashes would trip), the container image scan (the runtime target built from the shared registry buildcache, dockle with the publish lane's own tuned accept-key list, the trivy sarif report uploaded to code scanning, the critical gate — informational on push, the hard gates stay at publish time), and the cleanup contract (the gha caches a run creates are deleted when the pipeline finishes, the registry buildcache stays). The maintenance ladder's completion gate keeps firing on the green pipeline the informational scans preserve. |
+| The deno compatibility leg | The runtime compatibility matrix gains the deno leg the engines field always declared: the built deno entry answers deno check and the import smoke (the same battery the verify modes job runs, the saddle root-probe doctrine — every runtime the library declares carries its own compatibility lane). |
+| The mobile release signing surface | The android lane graduates from debug artifacts to the saddle release recipe: the sdkmanager platform and build-tools step, the version stamp that injects the keystore loader, the signingConfigs.release block and the r8-and-resource-shrinking release buildType, the signing three-way (the caller-owned keystore when the production secrets exist, the clearly labeled ci-test-key when a release fires without them, a hard fail on a manual build that carries neither), the apksigner and jarsigner verification of every shipped apk and aab, and the manifest recording which path answered. The ios ipa lane lands beside the simulator lane: the Apple keychain recipe (the distribution certificate and the provisioning profile the secrets carry, the export options plist), the xcodebuild archive and export, and the guard that keeps it off until the secrets or the repository variable exist — the simulator stays the no-secrets iOS surface. |
+| The tauri desktop shell | The desktop workflow gains the gui lane the saddle desktop surface always carried (a desktop application is not a virtualization surface — the whole lane ports): the seven-leg platform matrix (linux x64 and arm64, windows x86, x64 and arm64, macos x64 and arm64), the pinned rust toolchain the security lane's audit already pins (never the moving stable channel), the runner-side scaffold (the cargo manifest, the entry sources and the copied root tauri.conf.json with runner-relative paths — the native wrapper doctrine, the shell is toolchain output, never tracked), the icons derived on every leg from the new web/icon.svg source (the 1024px mark, nothing committed pre-rendered), the signed and unsigned build paths (the caller's windows certificate and the apple notarization when the secrets exist, the unsigned path otherwise), and the per-platform bundle assets beside the compiled binary lane. The root tauri.conf.json joins the version lockstep (the release sync stamps it with every bump), and the build/ workspace the lanes scratch joins the ignore file. |
+
+## 2.0.13 — the watchdog learns a finished check is a pass, the emulated leg answers green
+
+### Fixed
+
+| Area | Change |
+| --- | --- |
+| The container smoke race | The ghcr lane's arm64 leg died at the build-time smoke boot with "the container runner died" while the runner's own log carried the check's success line two seconds earlier — the qemu-emulated leg spawns each watchdog probe as a fresh node process that boots slowly enough for the runner to finish its whole check lifecycle (health endpoint, site index, relay refusal, mcp ping) and exit zero before the probe's fetch ever lands, so the closed server read as a dead one. The death branch of the smoke now waits for the runner's recorded exit status: a zero answers the pass the self-check already proved (the check mode exits nonzero the moment any surface misbehaves), a nonzero keeps the death message it always carried, and the post-healthz wait keeps catching a runner that dies after the watchdog sees it live. The emulated and the native legs answer the same smoke, and the native window the ladder always passed keeps its behavior byte for byte. |
+
 ## 2.0.12 — the interface dissolves into the web root, one folder serves every surface
 
 ### Changed