{"content":"IDBots v0.9.6 prep — build and publish an Intel (x64) macOS DMG\n\nCommit dd56a765 on branch feat/mac-x64-release.\n\nIDBots shipped macOS arm64 only, and the release chain hardcoded arm64 in four places. This change adds Intel x64 as a third artifact alongside the existing arm64 DMG and the Windows x64 installer:\n\n- build.yml: new macos-15-intel matrix entry building `--mac --x64`; a new `mac_arch` matrix field now drives every arch-dependent path (notarized app bundle, prepackaged DMG step, scripts/release-artifact-paths.cjs) instead of a hardcoded `mac-arm64`. A native Intel hosted runner is deliberate: pnpm then resolves the darwin-x64 siblings of the optional native packages dsh-runtime carries (~9 darwin-arm64 ones: cua-driver, sharp, ripgrep, sherpa-onnx, koffi, ...), which cross-building `--x64` from the arm64 runner could not do without embedding arm64 binaries into the Intel bundle.\n- release job: collect the x64 artifact and ship latest-mac-x64.yml in the GitHub Release.\n- release-finalize-yaml.cjs: rebuild one update manifest per arch from the FINAL signed DMGs. latest-mac.yml keeps its historic arm64 semantics; the Intel DMG gets latest-mac-x64.yml, so each arch's size/sha512 stays independently verifiable.\n- release-publish-oss-cdn.cjs: upload the Intel DMG and its manifest, and warm the x64 CDN URL.\n- release-runbook.mjs: include the Intel artifacts in download/verify/OSS, and fix the Windows OSS row, whose local file name and OSS object key were both wrong (SOP §9.1 maps the dotted local name to the hyphenated OSS object).\n\nNo in-app updater change is needed: src/renderer/services/appUpdate.ts already selects update.json's `macIntel` entry whenever the running arch is not arm64.\n\nVerified locally: build.yml parses and the matrix expands to three entries; the finalize script produces both mac manifests from two synthetic DMGs with sha512 matching openssl; release-runbook tests 4/4.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}