fix(action): pin CodeBoarding 0.13.10 - #100
Conversation
Ship the latest engine fixes and provider support through the action. Remove the explicit tqdm workaround now that Core declares its runtime dependencies itself.
CodeBoarding review · failedSee the workflow logs. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 16b23ce7b1
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # remove it once the engine declares its own. | ||
| run: | | ||
| python -m pip install --disable-pip-version-check 'codeboarding==0.13.8' tqdm | ||
| python -m pip install --disable-pip-version-check 'codeboarding==0.13.10' |
There was a problem hiding this comment.
When a job already exports ORCAROUTER_API_KEY but this action invocation selects another provider, the newly pinned engine recognizes OrcaRouter while scripts/action/with-auth.sh omits its variables from both the selectors list and provider-preserving case. The engine therefore receives an unrelated credential alongside the explicitly selected one, defeating the wrapper's provider isolation and potentially selecting or charging the wrong backend; add OrcaRouter variables to that filtering logic as part of this pin.
AGENTS.md reference: AGENTS.md:L12-L16
Useful? React with 👍 / 👎.
1 participant
What
codeboarding==0.13.10engine.tqdmworkaround because Core now declares that runtime dependency itself.Release path
Merge this PR before #99. The
fix(action):title is intentional: after squash merge, release-please will treat the engine update as release-worthy and refresh #99 to include it. Then merge the refreshed #99 to publish action 1.12.2 and move the major tag.If #99 is merged first, it will ship only the fixes currently listed there and this engine pin will require the next patch release instead.
Verification
python -m unittest discover -s tests -v(94 passed, including the protected merge-base tests)actionlintcodeboarding --helpstarts successfully