fix: update CodeBoarding dependency to 0.14.0 - #118
Conversation
CodeBoarding review · failedSee the workflow logs. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8a5d9de2d8
ℹ️ 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".
| shell: bash | ||
| run: | | ||
| python -m pip install --disable-pip-version-check 'codeboarding==0.13.11' | ||
| python -m pip install --disable-pip-version-check 'codeboarding==0.14.0' |
There was a problem hiding this comment.
Publish 0.14.0 before changing the install pin
If this commit is merged in its stated pre-publication state, the Install CodeBoarding step cannot resolve codeboarding==0.14.0, so every non-skipped review or sync run fails before analysis; the core-compatibility job also fails while installing the same requirement. Publish the distribution before merging this pin, or retain the latest published version until then.
AGENTS.md reference: AGENTS.md:L12-L16
Useful? React with 👍 / 👎.
Re-pin the analysis engine to codeboarding
0.14.0at its four sites: the install literal inaction.yml, theenginefield ofscripts/action/supported-providers.json, and the two README references (which had drifted to 0.13.10). Do not merge until0.14.0is published to PyPI — the install step runspip install codeboarding==0.14.0and thecore-compatibilityjob installs the pin. The action's provider table is unchanged: it matches 0.14.0'sLLM_PROVIDERS(drift test run locally against the release candidate).