Skip to content

ci: add workflow to auto-bump viam-cpp-sdk#75

Open
Ethan (stuqdog) wants to merge 2 commits into
viam-modules:mainfrom
stuqdog:bump-viam-cpp-sdk-workflow
Open

ci: add workflow to auto-bump viam-cpp-sdk#75
Ethan (stuqdog) wants to merge 2 commits into
viam-modules:mainfrom
stuqdog:bump-viam-cpp-sdk-workflow

Conversation

@stuqdog

@stuqdog Ethan (stuqdog) commented Jun 29, 2026

Copy link
Copy Markdown

Adds .github/workflows/bump-viam-cpp-sdk.yml — a daily scheduled workflow (plus workflow_dispatch) that opens/updates a PR bumping the viam-cpp-sdk conan pin in conanfile.py whenever a newer SDK release is published on viamrobotics/viam-cpp-sdk.

Why a custom workflow rather than Dependabot: the SDK is pinned via conan, which Dependabot has no ecosystem for.

  • Resolves the latest SDK release and the currently-pinned version; only bumps forward.
  • Rewrites the pin in conanfile.py.
  • Regenerates conan.lock via conan if the repo has one (realsense does; the #recipe-revision hash means a plain text replace is not enough).
  • Opens the PR with the org GIT_ACCESS_TOKEN bot secret (same one viam-python-sdk's update_protos uses) so the bump PR actually triggers CI.

Opened as a draft for review.

🤖 Generated with Claude Code


Also included: fix for the Windows CI break (unrelated to the SDK bump)

While opening this PR its build-module-windows check was failing — but not because of anything here. GitHub rolled the windows-latest image onto windows-2025-vs2026 (~2026-06-28), which ships Visual Studio 18 "2026". Conan then auto-selects the Visual Studio 18 2026 CMake generator, but abseil pins cmake<4 (→ cmake 3.31.9), which doesn't know that generator and fails to configure (Could not create named generator). Every dependency that resolved to cmake 4.1.2 (bzip2/c-ares/zlib/zstd) built fine on the same runner.

The second commit adds a one-line, abseil-scoped conan override in build.yml so abseil builds with cmake 4.x (which understands the new generator); all other deps are untouched. This is bundled here so the PR's own CI can go green.

Verified by comparing the passing 2026-06-08 run (image windows-2025, VS 2022, generator Visual Studio 17 2022) against the failing 2026-07-02 run (image windows-2025-vs2026, VS 18, generator Visual Studio 18 2026) — identical cmake recipes in both; only the runner's Visual Studio changed.

Adds .github/workflows/bump-viam-cpp-sdk.yml, a daily scheduled workflow that
opens a PR bumping the viam-cpp-sdk conan pin whenever a newer SDK release is
published. Dependabot has no conan ecosystem, so the bump is done explicitly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@stuqdog Ethan (stuqdog) marked this pull request as ready for review June 29, 2026 18:44
@stuqdog Ethan (stuqdog) requested review from a team and martha-johnston July 2, 2026 17:43
The windows-latest image was rolled onto windows-2025-vs2026 (~2026-06-28),
which ships Visual Studio 18 "2026". Conan then auto-selects the
"Visual Studio 18 2026" CMake generator, but abseil pins cmake<4 (3.31.9),
which doesn't recognize that generator and fails to configure. Force abseil
onto cmake 4.x (which does), leaving all other dependencies untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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