Skip to content

TaiChiOS 0.1.0-mvp.6

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Aug 08:11
v0.1.0-mvp.6
76e54be

TaiChiOS 0.1 MVP prerelease 6

本预发布版是 TaiChiOS 0.1 可启动、可安装系统基线的维护发布。它保持 mvp.5 已验收的 Debian 镜像、Harness 运行时、事务式变更、Guardian 与独立 Recovery 路径，同时升级 GitHub 构建来源证明动作并刷新官网依赖。它只适用于隔离的 x86_64 虚拟机，不适用于生产设备。

验收合同

发布流水线从同一标签构建二进制 ISO 与对应源码 ISO，并在发布前验证：

  • 固定的 Cordis、DeepSeek Harness、Node.js 与 dsh-TUI 组合可离线启动；
  • BIOS 与 UEFI 均可在无网络环境启动 Live 系统；
  • BIOS 与 UEFI 均可执行整盘安装，移除 Live 介质并断网后可从硬盘启动；
  • Guardian、Safe Profile、Recovery 与事务式 Change Set 验收保持通过；
  • 生成包/源码清单、SHA-256 校验和、发布元数据、构建环境记录与 GitHub 构建来源证明。

请下载 taichios-0.1-amd64.hybrid.iso 并使用 SHA256SUMS 验证。Release 同时提供对应源码 ISO、源码/包清单、构建环境与机器可读兼容性元数据。

相比 mvp.5 的变化

  • 将 actions/attest-build-provenance 从 v3 升级到 v4，发布制品继续生成 GitHub build-provenance attestation。
  • 将官网 lucide-react 从 1.33.0 升级到 1.34.0。
  • 将官网 @types/node 从 24.10.1 升级到 24.13.3，并随 lockfile 将 undici-types 更新到 7.18.2。
  • Debian snapshot、Node.js 镜像运行时、Cordis、DeepSeek Harness 与 dsh-TUI 固定版本不变；本次没有新增系统迁移或磁盘格式变更。

迁移、失败与恢复

  • 从 mvp.5 升级没有自动的跨版本原地迁移器；推荐在隔离虚拟机中全新安装 mvp.6。
  • 托管文件和 /opt/taichios system-update 可使用已记录 Rollback Point 恢复；缺少回滚点或恢复失败会保留 rollback-failed 证据。
  • Guardian/Harness 故障可回退到 Safe Profile 或独立 Recovery；Recovery 不提供任意 Debian 包状态的跨版本完整回滚。
  • 如 mvp.6 无法满足需求，可重新安装经校验的 mvp.5 镜像；用户数据迁移仍需人工备份与恢复。

限制

  • 工厂凭据只用于开发验收；尚未实现生产凭据注册。
  • 默认 Provider 是离线 mock；尚未实现持久身份、加密 Secret 存储、配额、健康检查和生产 Provider adapter。
  • 固定镜像策略仍禁用 Secure Boot 与额外固件。
  • 社区插件尚未具备生产级来源验证、授权和强制执行隔离。
  • 本预发布版没有生产安全 SLA。请通过 GitHub Security Advisories 报告漏洞。

English

This maintenance prerelease preserves the verified TaiChiOS 0.1 bootable and installable system baseline while upgrading GitHub build-provenance attestation and refreshing website dependencies. It is intended for isolated x86_64 virtual machines, not production devices.

Acceptance contract

The release workflow builds the binary ISO and corresponding-source ISO from the same tag, then gates publication on:

  • offline startup of the pinned Cordis, DeepSeek Harness, Node.js, and dsh-TUI combination;
  • BIOS and UEFI Live boot without networking;
  • whole-disk installation under BIOS and UEFI, followed by disk boot without the Live medium or networking;
  • continued Guardian, Safe Profile, Recovery, and transactional Change Set acceptance;
  • package/source manifests, SHA-256 checksums, release metadata, build-environment recording, and GitHub build-provenance attestation.

Download taichios-0.1-amd64.hybrid.iso and verify it with SHA256SUMS. The Release also contains the corresponding-source ISO, source/package manifests, build environment, and machine-readable compatibility metadata.

Changes since mvp.5

  • Upgrades actions/attest-build-provenance from v3 to v4 while retaining GitHub build-provenance attestation for release payloads.
  • Upgrades the website's lucide-react from 1.33.0 to 1.34.0.
  • Upgrades the website's @types/node from 24.10.1 to 24.13.3 and refreshes lockfile-pinned undici-types to 7.18.2.
  • Keeps the Debian snapshot and pinned Node.js image runtime, Cordis, DeepSeek Harness, and dsh-TUI versions unchanged; this release adds no system migration or disk-format change.

Migration, failure, and recovery

  • There is no automated in-place cross-version migrator from mvp.5; use a clean mvp.6 installation in an isolated virtual machine.
  • Managed files and the /opt/taichios system-update pointer can use a recorded Rollback Point. A missing rollback point or failed restore retains rollback-failed evidence.
  • Guardian/Harness failures can fall back to Safe Profile or independent Recovery. Recovery does not provide arbitrary cross-version rollback of Debian package state.
  • If mvp.6 is unsuitable, reinstall the verified mvp.5 image; user-data migration still requires manual backup and restore.

Limitations

  • Factory credentials remain development-only; production credential enrollment is not implemented.
  • The default Provider is an offline mock. Persistent identity, encrypted Secret storage, quotas, health checks, and production Provider adapters are not implemented.
  • Secure Boot and additional firmware remain disabled by the pinned image policy.
  • Community plugins do not yet have production-grade provenance validation, authorization, or enforced execution isolation.
  • This prerelease has no production security SLA. Report vulnerabilities through GitHub Security Advisories.
Assets 11
Loading