Skip to content

chore: upgrade template subtree to v0.10.0-rc2#28

Merged
ycpss91255 merged 5 commits intomainfrom
chore/upgrade-template-v0.10.0-rc2
Apr 24, 2026
Merged

chore: upgrade template subtree to v0.10.0-rc2#28
ycpss91255 merged 5 commits intomainfrom
chore/upgrade-template-v0.10.0-rc2

Conversation

@ycpss91255
Copy link
Copy Markdown
Contributor

Summary

Straight jump from @v0.9.13 to @v0.10.0-rc2. Bundles all intermediate template releases:

Template Highlight
v0.9.11 arm64-native CI matrix + Jetson auto-detect (already in prior PRs)
v0.9.12 build-worker load: true attempt (latent bug, superseded)
v0.9.13 GHCR test-tools D plan + build-worker.yaml GHCR pull
v0.10.0-rc1 runtime compose service auto-emission (#108); run.sh arg realignment (#118, BREAKING)
v0.10.0-rc2 Dockerfile.test-tools ARG TARGETARCH default fix — arm64 variants now ship real aarch64 binaries

Changes

  • template/ subtree squashed pull → v0.10.0-rc2 (auto via ./template/upgrade.sh v0.10.0-rc2).
  • main.yaml @v0.9.13@v0.10.0-rc2 (one workaround commit fixes a latent upgrade.sh sed regex bug — -rc2-rc2 double-suffix, details in commit body).
  • CHANGELOG rewritten to reflect the rc2 landing (skipping the intermediate CHANGELOG language).

Validation (local, amd64)

  • ./build.sh --no-env test — 28/28 smoke tests pass, lint green.
  • compose.yaml contains devel / runtime / test services (auto-emitted by v0.10.0-rc2 setup.sh after it saw FROM devel AS runtime in Dockerfile).
  • ./run.sh --dry-runcompose up -d devel && compose exec devel bash (unchanged UX).
  • ./run.sh --dry-run -t runtime bashcompose run --rm runtime bash (cmd override).
  • ./run.sh --dry-run -d lsexit 2 with actionable error pointing at ./exec.sh.

Pending (next PRs, not this one)

  • Template side: upgrade.sh sed regex bug fix so future RC upgrades stop producing -rcN-rcN (this PR contains a one-line workaround; template fix will close the hole and ship in v0.10.0 stable).
  • This repo's dev_bridge / demo scripts (PR feat: 2-terminal demo scripts for ROS 1 <-> ROS 2 bridge #26) — independent branch.

Test plan

  • CI call-docker-build / build (linux/amd64, ubuntu-latest, x86_64) green
  • CI call-docker-build / build (linux/arm64, ubuntu-24.04-arm, aarch64) green — this is the first time arm64 exercises the v0.10.0-rc2 test-tools + runtime compose service.

7b260c4f chore: release v0.10.0-rc2 (#127)
ef0883ab fix: remove ARG TARGETARCH default in Dockerfile.test-tools (#126)
76aab349 chore: release v0.10.0-rc1 (#123)
4a3a2636 feat: runtime compose service + run.sh cmd passthrough (#108, #118) (#122)
daa81cf6 chore: release v0.9.13 (#121)
6bb8a5ec fix(ci): release-test-tools Dockerfile path (drop subtree prefix) (#120)
16af321d feat: migrate test-tools to pre-built GHCR image (closes #106) (#119)
526337d0 chore: release v0.9.12 (#117)
bf34361b fix(ci): build-worker.yaml test-tools build must use load:true (#116)
846b6f00 feat: add dependabot.yml + document upgrade.sh automation (#110)

git-subtree-dir: template
git-subtree-split: 7b260c4fe56b88077567c9e1775ef1047c8ab5aa
- main.yaml: workflow @tag updated to v0.10.0-rc2
template/script/docker/upgrade.sh's main.yaml @tag sed uses
`[0-9.]*` character class which stops at the first `-`, so upgrading
to `v0.10.0-rc2` leaves the existing `-rc2` suffix untouched and
prepends a new one → ends up as `@v0.10.0-rc2-rc2`. Fixed manually
in this branch.

Template-side fix tracked separately (upgrade.sh regex should accept
semver pre-release suffixes like `[0-9A-Za-z.-]*` or a grouped
`\d+\.\d+\.\d+(-[0-9A-Za-z.-]+)?` capture).
Reflects the intermediate rc2 landing: runtime compose service,
run.sh arg realignment (BREAKING — `-t target` flag + cmd passthrough),
and the arm64 test-tools binary hotfix. Calls out that
v0.9.11 / v0.9.12 / v0.9.13 / v0.10.0-rc1 are superseded and this PR
skips straight to @v0.10.0-rc2.
@ycpss91255 ycpss91255 merged commit a31a337 into main Apr 24, 2026
5 checks passed
@ycpss91255 ycpss91255 deleted the chore/upgrade-template-v0.10.0-rc2 branch April 24, 2026 11:09
@ycpss91255 ycpss91255 mentioned this pull request Apr 24, 2026
3 tasks
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.

1 participant