Skip to content

release-metadata: draft v2.0.0-rc.1 notes, proposed pins and integration snapshot - #18

Draft
BotshareAI wants to merge 12 commits into
mainfrom
release/v2.0.0-rc.1-draft-notes
Draft

BotshareAI wants to merge 12 commits into
mainfrom
release/v2.0.0-rc.1-draft-notes

Conversation

@BotshareAI

@BotshareAI BotshareAI commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Summary

v2.0.0-rc.1 release metadata, stacked on the rc.1 builder #12 so it applies as soon as #12 merges.

No tag, no GitHub Release. Simulation is development evidence, not physical or safety acceptance.

Precondition

  • Repository: openAMRobot/openamrobot-release
  • Branch: release/v2.0.0-rc.1-draft-notes
  • Parent SHA: 91c7458 (previous head)
  • Expected outcome: fast-forward push of three commits; draft stays draft until the owner writes adopt, adapt or reject.

Integration Gate

Tests

Base SHA: c39eda7
Head SHA: 18bb3c8 (7854335 plus one notes commit)

python3 -m unittest discover -s tests                     # 35 tests, OK (local and CI run 44741406359)
python3 scripts/lock_release_sources.py --manifest manifests/v2.0.0-rc.1.repos --output release-config.rc1.next.json --cache-dir <cache> --version 2.0.0-rc.1
python3 scripts/build_release.py --config release-config.rc1.json --input-dir <in-first> --output-dir <dist-first> --fetch    # PASS: 3061 files verified
python3 scripts/build_release.py --config release-config.rc1.json --input-dir <in-second> --output-dir <dist-second> --fetch  # PASS: 3061 files verified
python3 scripts/validate_release.py <dist-first>/OpenAMRobot-v2.0.0-rc.1-source.zip    # PASS (same for second)
cmp <dist-first>/OpenAMRobot-v2.0.0-rc.1-source.zip <dist-second>/OpenAMRobot-v2.0.0-rc.1-source.zip   # identical
(cd <dist-first> && sha256sum -c OpenAMRobot-v2.0.0-rc.1-source.zip.sha256)                          # OK
python3 scripts/check_manifest_sync.py manifests/v2.0.0-rc.1.repos <manifest clone with the patch>/releases/v2.0.0-rc.1.repos   # Matched 14 repositories

Trial build result (both builds): 657ed9b3aa59d9c669af53bcf1ff2612d1b068c969af3cd966b9d76ae1f6530c, 400568111 bytes. Unchanged entries (upperbody-fw, sllidar_ros2, micro_ros_agent) kept their 19 Oct source hashes, so the lock tool is stable across a month.

Revert run: the 19 Oct lock against the new manifest stops the build (ValueError: manifest checksum mismatch, exit 1).

openamrobot-manifest patch: pytest tests 42 passed with yamllint and vcstool installed (main: 42 passed in the same environment); check_manifest.py --offline PASS 14 repositories; check_release_manifest.py --development PASS.

Not verified

  • The trial builds ran locally, not in CI: the CI build steps are skipped behind the parity failure until openamrobot-manifest carries the pins.
  • openamrobot-manifest's hosted workflows (vcs import, Jazzy driver sources) did not run on the patch.
  • CI for openamrobot-comm, openamrobot-manipulation, openamr-upperbody-hw and .github was not read.
  • git diff --check reports trailing whitespace only inside the .patch file (context lines of the patch format).
  • No simulation was re-run for this PR. No physical, electrical or safety verification of anything.

STATE.md

Updated (#12's file), paragraph dated 2026-11-20.

Dependencies

No change by these commits. Through the #12 merge the diff shows requirements-release.txt with PyYAML 6.0.3 (MIT, https://github.com/yaml/pyyaml), as reviewed in #12.

Safety impact

None. Release metadata and pins only. No safety-path file touched.

AI disclosure

Claude Code (Claude Opus 5.5) merged #12 into this branch, wrote the manifest, regenerated the lock, ran the trial builds, wrote the runbook, the openamrobot-manifest patch, the notes refresh and this description.

Intellectual property and provenance

  • Every commit is signed off under the OpenAMRobot DCO.
  • I am covered by an accepted Individual or Corporate Contributor Agreement. (for the contributor to answer)
  • I have all required employer, university, client, sponsor, co-author, or institutional authorization. (for the contributor to answer)
  • Third-party and material AI-assisted content is identified with source, licence, modifications, and notices.
  • No unauthorized confidential, personal, proprietary, credential, or export-controlled information is included.

https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF


Generated by Claude Code

KARTHIKEYAN124 and others added 10 commits October 24, 2026 16:54
Signed-off-by: Karthikeyan <mahikarthik10@gmail.com>
Signed-off-by: Karthikeyan <mahikarthik10@gmail.com>
Signed-off-by: Karthikeyan <mahikarthik10@gmail.com>
Signed-off-by: Karthikeyan <mahikarthik10@gmail.com>
Signed-off-by: Karthikeyan <mahikarthik10@gmail.com>
Signed-off-by: Karthikeyan <mahikarthik10@gmail.com>
…ion snapshot

Draft release notes for v2.0.0-rc.1 with a status table per subsystem,
known limitations, safety statement and a manifest of proposed pins
(reviewed main of each repository). Baseline 1 integration branches are
recorded separately as an integration snapshot, not release content.
No tag, no release, no lock change.

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF
Stacks the notes and the pin refresh on the adopted rc.1 builder so they
apply as soon as #12 merges. No change to #12's files in this merge.

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF
manifests/v2.0.0-rc.1.repos moves from the 2026-10-19 candidate to the
SHAs proposed in release-metadata/v2.0.0-rc.1 (read 2026-11-20) and adds
openamrobot-embodied-ai; pins.proposed.repos is removed because the
manifest now carries them. release-config.rc1.json is regenerated with
scripts/lock_release_sources.py from that manifest. Two local fetch
builds: identical zips, sha256 657ed9b3...6530c, 400568111 bytes.

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF
…shed

RUNBOOK.md: merge order (#12, optional upperbody-sw #74, the
openamrobot-manifest parity change, #18), CI or local build, checksum
check, draft release, the Baseline 1 decision and the switch to
pre-release. openamrobot-manifest-rc1-pins.patch carries the same pins
for openamrobot-manifest (42 tests pass locally). Notes: trial build
checksum, #169 approved, upperbody reviews of 20 Nov, #74 tag and pin
changes, integration head c0af973. No status raised.

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF
BotshareAI and others added 2 commits November 20, 2026 13:24
…repin

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF
… heads

RUNBOOK.md, checked command by command on 20 Nov (PowerShell 7 and bash;
GitHub-changing steps checked against settings and rules only):
- step 0 compares all 15 pins in one command (micro-ROS-Agent on jazzy);
- step 1: the repository allows squash only, so merge commits must be
  enabled first; #12 needs a code-owner approval (BotshareAI), the
  software lead is not a code owner here;
- step 3: patch fetched at 18bb3c8 with its sha256, autocrlf off, PR body
  file with the pushed head SHA filled in, reviewers named, manifest #22
  named as overlapping;
- step 4: #18 is BotshareAI's own PR, KARTHIKEYAN124 approves; rerun and
  merge commands;
- steps 5, 6, 9, 10: run ID capture, one-line checksum comparison,
  tag check; step 8 is the publication-day status refresh with the exact
  conditions for a qualifying strict Baseline 1 run; D4 options.

integration-snapshot.repos and the notes: upperbody-sw integration head
c0af973 -> 196dd3f (platform-sw unchanged at fb25be1), still not release
content. README: the v0.0.1 Raspberry Pi 5 is labelled legacy (COMPUTE).
Pins and lock unchanged; one local fetch build matched 657ed9b3...6530c.

Signed-off-by: Alex Reznichenko <info@botshare.ai>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZnPEMPDB6f8AohTTfGWkF
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants