chore: qsl runtime compatibility metadata#296
Conversation
Co-Authored-By: Codex <noreply@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 392035d520
ℹ️ 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".
| quant_platform_kit = "0063af3b4a974650ea58a7d3f26dd1b94f65d3e8" | ||
| us_equity_strategies = "46887bc3f5454d5b59623b1f5efb7c65912c6b8b" | ||
| hk_equity_strategies = "61993bf261aeccf64b5a75428b9405f4e1d1d682" |
There was a problem hiding this comment.
These new qsl.requires SHAs duplicate the install pins in pyproject.toml, but the blocking CI guard only runs scripts/check_qpk_pin_consistency.py, whose PINNED_FILE_GLOBS at line 22 omits qsl.toml (the workflow invokes that guard at .github/workflows/ci.yml:113). When the normal dependency bump updates pyproject.toml/uv.lock, this metadata can silently stay on the old bundle and compatibility automation will consume stale pins; please add this file to the guard or make the test compare it to the actual dependency pins.
Useful? React with 👍 / 👎.
Co-Authored-By: Codex <noreply@openai.com>
Summary\n- Add qsl.toml metadata for compatibility runtime upgrade mode.\n- Add minimal metadata tests for runtime repos where applicable.\n- For Binance: keep requirements/pip stack and add migration TODO note.\n- For IBKRGatewayManager/SchwabTokenAutoRefresher: metadata-only for non-Python package tooling.