Skip to content

Your lightweight open-source personal agent.

chore(release): prepare v0.3.5 (NAN-110)

Xubin Renea630c73038a
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 85a603c45..c9dfc524e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -138,6 +138,9 @@ explicitly in the PR description so it can be discussed before merge.
## Release Packaging Contract
+Use the [release checklist](./docs/releasing.md) for candidate preparation, package checks,
+documentation coordination, and the final publication handoff.
+
A stable install must never combine Python from one version with a TUI from another. Publish in
this order:
diff --git a/docs/releasing.md b/docs/releasing.md
new file mode 100644
index 000000000..8f8be6691
--- /dev/null
+++ b/docs/releasing.md
@@ -0,0 +1,64 @@
+# Release checklist
+
+Use this checklist with the [Release Packaging Contract](../CONTRIBUTING.md#release-packaging-contract).
+Preparing a release does not publish it. Pushing a Git tag, publishing a GitHub Release,
+uploading to PyPI, and deploying the documentation are separate operations.
+
+## Prepare a candidate
+
+1. Choose the previous release and the exact candidate commit. Work in a clean worktree;
+ do not include local configuration, session data, credentials, or unrelated changes.
+2. Update `project.version` in `pyproject.toml` and the final source-only fallback in
+ `nanobot/__init__.py`. Private WebUI/TUI package versions are not the Python release version.
+3. Review the changes since the previous tag. Write highlights, upgrade and rollback guidance,
+ contributor acknowledgements, and the full changelog. Verify counts against the final
+ range; commit counts are not merged-PR counts. Coordinate security disclosures separately.
+4. Run the Python, WebUI, and TUI checks from CI. Confirm the final commit's CI status, not
+ just an earlier PR head. Review installation, configuration, session, and API changes.
+5. Build in a clean output directory with `uv build --out-dir <artifact-directory>`.
+ Do not set `NANOBOT_SKIP_WEBUI_BUILD`. The build hook bundles the WebUI in the sdist and
+ wheel; the wheel is built from the sdist.
+6. Check the two distributions with `twine check`, inspect their contents, and record SHA-256
+ hashes. Test installation in an isolated environment outside the source checkout, then
+ test upgrading from the previous stable version using disposable configuration and sessions.
+ Do not use a maintainer's live workspace for migration tests.
+7. Prepare the matching documentation PR in `Re-bin/nanobot-web`, following its
+ `MAINTAINING.md`. Review English and all nine translations, preserve Nightly and previous
+ releases, update the latest-version redirects, and run the complete site quality gate.
+ Candidate docs may be prepared from a commit, but must be checked against the final tag.
+
+Keep an artifact manifest with the source commit, version, filenames, hashes, checks performed,
+and any remaining release gates. Rebuild and recheck if the packaged source changes.
+
+## Publish, with maintainer approval
+
+1. Merge the release-preparation PR and confirm the final commit. Create and push exactly
+ `vX.Y.Z`; do not move or reuse a published version tag.
+2. Create the matching GitHub Release. A draft may be used while assembling its attachments.
+ Pushing the tag alone does not run `Publish Terminal UI` or upload anything to PyPI.
+3. Review the pinned Bun/OpenTUI licenses, corresponding-source materials, source-offer
+ commitment, and relinking instructions for that exact tag. Only then confirm the
+ compliance input and manually run **Publish Terminal UI** with `tag=vX.Y.Z`.
+4. Wait for all five targets: macOS arm64/x64, Linux arm64/x64, and Windows x64. Each needs
+ its release archive and `.sha256` file. Check the archive contents required by the
+ packaging contract. A successful build is not a substitute for compliance review.
+5. Make the GitHub Release and all TUI attachments publicly available. Verify their public
+ downloads before publishing Python, since installed clients fetch version-matched assets.
+6. Upload only the checked `nanobot_ai-X.Y.Z.tar.gz` and `nanobot_ai-X.Y.Z-py3-none-any.whl`
+ to PyPI. Do not upload stale files from a shared `dist/` directory. This repository has no
+ automatic PyPI publication workflow.
+7. Verify installation from PyPI, bundled WebUI startup, and the matching TUI download in
+ clean environments. Merge the prepared wiki PR only when the stable package is available:
+ merging its `main` deploys the site automatically. Confirm all localized `/docs/latest/`
+ routes select the new version and old version links still work.
+8. Publish the release announcement and add the dated entry to
+ [Release Archive](./release-archive.md). Complete any coordinated advisory publication and
+ reporter notification. Record links and completion status in the release tracking issue.
+
+## If a gate fails
+
+Do not publish to PyPI while a required TUI artifact or verification is missing. Keep the
+documentation's public `latest` on the previous stable version until the new version is usable.
+If a published package needs a correction, prepare a new version; do not silently replace
+the code behind an existing release tag. Stop all old processes and follow the documented
+session rollback procedure before downgrading a migrated installation.
diff --git a/nanobot/__init__.py b/nanobot/__init__.py
index 215dd80c8..ac09e67e1 100644
--- a/nanobot/__init__.py
+++ b/nanobot/__init__.py
@@ -49,7 +49,7 @@ def _resolve_version() -> str:
return _pkg_version("nanobot-ai")
except PackageNotFoundError:
# Source checkouts often import nanobot without installed dist-info.
- return _read_pyproject_version() or "0.3.0"
+ return _read_pyproject_version() or "0.3.5"
__version__ = _resolve_version()
diff --git a/pyproject.toml b/pyproject.toml
index 57ac30ed1..2734c2452 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,6 @@
[project]
name = "nanobot-ai"
-version = "0.3.0"
+version = "0.3.5"
description = "A lightweight personal AI assistant framework"
readme = { file = "README.md", content-type = "text/markdown" }
requires-python = ">=3.11"