fix: update CodeBoarding dependency to 0.13.3#59
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Architecture review · failedThe architecture diff couldn't be generated for this run. See the workflow logs for details. codeboarding-action · run 29961407232 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b95892c5e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| description: 'CodeBoarding PyPI package version used as the analysis engine. Pin for reproducibility; set to a newer released version to opt into newer engine releases.' | ||
| required: false | ||
| default: '0.13.2' | ||
| default: '0.13.3' |
There was a problem hiding this comment.
Do not default to an unpublished engine version
As of July 22, 2026, the PyPI release history lists codeboarding 0.13.2 as the latest release and does not include 0.13.3, but the action install step turns this default into codeboarding==0.13.3 before running pip install. With default inputs, every review/sync workflow will fail during package installation until 0.13.3 is actually published, so this should either stay pinned to the latest published version or be merged only after the release exists.
Useful? React with 👍 / 👎.
Re-pin the analysis engine to
codeboarding0.13.3:action.yml—codeboarding_versioninputdefault→0.13.3README.md— inputs-table row and thepip install codeboarding==example →0.13.3(these had drifted a version behindaction.yml; now realigned)codeboarding==0.13.3is published to PyPI — the install step runspip install codeboarding==0.13.3, so merging earlier would break consumers' next run and the repo's own dogfood CI.The action's own version is release-please managed and is intentionally untouched here.