chore(deps): align QPK pin to 31892425a022 - #333
Conversation
Automated downstream QPK pin update after QPK_PIN landed on main. Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Codex PR Review✅ Merge allowed: No issues found Review by Codex PR Review bot • PR |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b5f49dcc24
ℹ️ 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".
| "google-cloud-storage", | ||
| "yfinance", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@56a03364d517fd0e2efb2c4d4add8a785fc5e857", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@31892425a02242126265ac07a626d98796daa459", |
There was a problem hiding this comment.
Align QPK pin with the checked-out QPK_PIN
In the current CI workflow (.github/workflows/ci.yml:113-118), the pin guard runs external/QuantPlatformKit/scripts/check_qpk_pin_consistency.py --pin-file external/QuantPlatformKit/QPK_PIN, so it compares this pyproject.toml ref against the QPK_PIN file from the checked-out QuantPlatformKit repo. The QPK_PIN at the referenced QPK commit 31892425a022... points at 618b786d..., and the default QPK main currently points at 56a03364..., so this repo's new 31892425... pin is not the canonical pin in either path CI can use and the consistency check will fail before tests. Please pin to the canonical QPK_PIN value, or advance QPK_PIN first, rather than pinning to the QPK commit itself.
Useful? React with 👍 / 👎.
Summary
31892425a022uv.lock,同步刷新 lockfileTest plan
🤖 Generated with Claude Code