Repository navigation
Publish Conan packages and sync Jira when a release is published - #725
Merged
Merged
Conversation
Both ran only on manual dispatch, so the GitHub release could name a version viamconan lacked for hours; 0.42.0 went 11 hours. A release event publishes with the lockfile and RelWithDebInfo and without deps, the inputs the 0.42.0 dispatch used. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Ale Paredes (ale7714)
requested review from
lia (lia-viam) and
Ethan (stuqdog)
and removed request for
a team
October 16, 2026 16:27
lia (lia-viam)
approved these changes
Oct 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A release takes four manual steps: build the draft, publish it, dispatch "Publish conan packages", dispatch "Sync Release to Jira". For 0.42.0 the release went public at 04:32 UTC on 2026-10-15 and the Conan publish ran at 15:35, so for 11 hours the latest GitHub release named a version viamconan didn't have. overwatch's weekly bump ran in that gap and opened viam-modules/csi-camera#79 with a
conanfile.pypin itsconan.lockcouldn't satisfy; viamrobotics/overwatch#76 makes that bump wait for the recipe.With both workflows on
release: published, the 0.42.0 timings put the recipe on viamconan about 10 minutes after publishing and every leg done in 26. A release event uses the inputs the 0.42.0 dispatch used: lockfile and RelWithDebInfo on, deps off.workflow_dispatchstays for re-runs and dep uploads.GitHub runs a release event's workflow from the tagged commit, so this takes effect from the first release cut after merge. The trigger fires when a person publishes in the UI, not when a workflow publishes with
GITHUB_TOKEN. Only a real release exercises it: I ran the params step's shell locally, and actionlint reports no findings beyond the 10 already on main.🤖 Generated with Claude Code