diff --git a/CHANGELOG.md b/CHANGELOG.md index 0910d0e..38ccd5a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,8 +4,9 @@ All notable changes to WAMProbe will be documented here. ## [0.1.0rc1] - 2026-07-15 -This candidate is prepared for reproducibility review and is not yet published to PyPI or -as a final GitHub Release. +This candidate is published as a +[GitHub pre-release](https://github.com/myheart521/WAMProbe/releases/tag/v0.1.0rc1) for +reproducibility review. It is not yet published to PyPI or as a final GitHub Release. ### Added diff --git a/README.md b/README.md index 3de4122..6c58889 100644 --- a/README.md +++ b/README.md @@ -142,6 +142,15 @@ PYTHONPATH=src python -m wamprobe demo --output runs/pointmass-demo - Python 3.11–3.13 CI with linting, strict typing, coverage, public JSON Schema validation, repository-local Markdown link checking, and a strict documentation build. +## Release candidate + +[`v0.1.0rc1`](https://github.com/myheart521/WAMProbe/releases/tag/v0.1.0rc1) is +available as a GitHub pre-release with an audited wheel, source distribution, release +manifest, and GitHub build-provenance attestations. Independent users can report a clean +installation smoke in [Issue #2](https://github.com/myheart521/WAMProbe/issues/2). PyPI +publication remains pending the one-time Trusted Publisher registration for this new +project; until then, install the wheel attached to the GitHub pre-release. + ## Roadmap The next milestones are: @@ -149,8 +158,8 @@ The next milestones are: 1. expand LIBERO initial states and evaluate action-conditioned real-WAM futures when an adapter exposes that capability; 2. add the Occluded-Object memory diagnostic to the broader Toy tier; -3. obtain an independent reproduction smoke, then review the candidate for explicit - maintainer-approved PyPI/GitHub publication. +3. finish the one-time PyPI Trusted Publisher registration, obtain an independent + reproduction smoke, then review the candidate for a final `v0.1.0` release. See the [detailed Chinese project plan](docs/WAMProbe_PLAN.md), [quick-start notes](docs/QUICKSTART.md), [failure-case evidence map](docs/research/WAM_VLA_FAILURE_CASES.md), diff --git a/docs/WAMProbe_PLAN.md b/docs/WAMProbe_PLAN.md index 4ba4623..6abfd6f 100644 --- a/docs/WAMProbe_PLAN.md +++ b/docs/WAMProbe_PLAN.md @@ -1126,8 +1126,12 @@ return 的 5-profile 描述性 Pearson 分别为 0.9855/1.0。全部结果、con 与 [`docs/experiments/TOY_CLOSED_LOOP_V0.1.md`](experiments/TOY_CLOSED_LOOP_V0.1.md)。 `0.1.0rc1` 候选版本现已具备双构建 SHA 一致性、归档安全/metadata 审计、证据 manifest、 离线干净 wheel 安装 smoke、手动 provenance attestation workflow,并提供可在 Overleaf -直接编译的 5 页技术报告初稿。正式 PyPI/GitHub Release、上游 PR 和外部用户复现仍需 -维护者或第三方授权,未被自动触发。 +直接编译的 5 页技术报告初稿。`v0.1.0rc1` 已作为 GitHub pre-release 发布,wheel 与 +sdist 的 provenance attestation 已登记;外部复现请求见 +[`WAMProbe#2`](https://github.com/myheart521/WAMProbe/issues/2),StarWAM 第三方评测入口见 +[`StarWAM#2`](https://github.com/shaohua-pan/StarWAM/pull/2)。PyPI 首次发布仍等待在 PyPI +登记 Pending Trusted Publisher,Overleaf 上传仍等待可用的账户登录态;独立用户 smoke +在收到真实第三方报告前保持未完成。 任务: diff --git a/release/README.md b/release/README.md index fa63dec..d64a37c 100644 --- a/release/README.md +++ b/release/README.md @@ -33,10 +33,17 @@ provenance attestations. It is manual-dispatch only. ## Public release boundary +The audited `v0.1.0rc1` artifacts are available from the +[GitHub pre-release](https://github.com/myheart521/WAMProbe/releases/tag/v0.1.0rc1), and +the wheel and sdist have GitHub build-provenance attestations. The independent clean-smoke +request is tracked in [Issue #2](https://github.com/myheart521/WAMProbe/issues/2). PyPI +publication is pending the one-time Trusted Publisher registration for this new project. + Before publishing, a maintainer must review the candidate manifest, confirm the version and changelog, obtain one independent clean-environment smoke report, configure the PyPI Trusted Publisher for the repository/environment, and approve both the Git tag and GitHub -Release text. Public `v0.1.0` publication is intentionally not automated from this Draft PR. +Release text. Final `v0.1.0` publication remains a separate maintainer decision after the +release-candidate review. The guarded `Publish to PyPI` workflow is manual-dispatch only, runs only when the selected ref is a tag, requires the typed confirmation to equal that tag, verifies that