[RELEASE] Validate clean installation and generated interface consumption #5

Activity

1. panthera-momagdii commented on Sep 28, 2026

   

   panthera-momagdii

   on Sep 28, 2026 – with ChatGPT Codex Connector

   More actions

   @KARTHIKEYAN124 This is the next concrete item for you after the interface CI work. #6 is now complete/closed; interfaces #7 is a tracking issue, not a separate implementation task.

   Please coordinate this release/install evidence with Arumuga:

   1. choose and record the exact openamrobot-interfaces commit/package versions to install;
   2. reproduce a clean install with no developer overlay/source tree dependency;
   3. verify generated openamr_nav_msgs are available after install;
   4. build/run a minimal downstream consumer against only the installed package;
   5. add the pinned entry + contract version to the release manifest;
   6. link install/troubleshooting instructions and attach the exact commands/logs as evidence.

   The existing clean-workspace consumer in interfaces #10 is useful input, but this issue needs release-level pinned-install evidence.
2. KARTHIKEYAN124 commented on Oct 9, 2026

   

   KARTHIKEYAN124

   on Oct 9, 2026

   Member

   More actions

   Release-level pinned-install implementation and evidence are available in PR #9.

   All six requested technical items are covered:

   1. Exact interfaces pin: fa7c438e33bd807c174fa0747119d7d627faa3bf; openamr_nav_msgs package 0.0.0; runtime contract 1, recorded in the installation manifest.
   2. Two independent clean producer/consumer pairs passed on Ubuntu 24.04 / ROS 2 Jazzy / linux amd64 with a digest-pinned image. Consumer containers receive only the installed tarball and test fixtures, with no interfaces source/build tree or developer overlay.
   3. All 11 generated navigation messages passed lookup, import, and native serialization/deserialization.
   4. The downstream C++ consumer built, linked and ran twice against only the installed package plus ROS dependencies. The absent-install negative control failed as expected in both runs.
   5. The candidate release builder records the pin, package version, contract version and evidence. The generated component entry and eight passing manifest tests cover this integration.
   6. Install/troubleshooting instructions are linked from README and RELEASE_PROCESS. Exact commands and log index, complete local evidence ZIP, and ZIP checksum are published.

   Hosted verification: successful GitHub Actions run and complete hosted evidence artifact. I downloaded the hosted artifact and verified every recorded checksum; both clean install/consumer runs passed. Generated header/IDL hashes, expanded definitions and dependency inventories matched between runs. DCO, CLA and repository-quality checks also pass.

   This proves a pinned source-install candidate and release-manifest integration. No binary package publication or full product release is claimed. The PR remains open for merge.
3. BotshareAI

   closed this as completedin #9on Oct 24, 2026