chore(deps): align QPK pin to 2dee23c125c0#227
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: 6202b3a5e4
ℹ️ 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".
| "pytz", | ||
| "requests", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@56a03364d517fd0e2efb2c4d4add8a785fc5e857", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@2dee23c125c0b1b60946b3bf9e48ce75991bba36", |
There was a problem hiding this comment.
Pin QPK to the canonical QPK_PIN
When this branch is validated against QuantPlatformKit main (the CI resolver falls back to main when no matching QPK branch exists, and push-to-main runs also use main), the external check_qpk_pin_consistency.py --pin-file external/QuantPlatformKit/QPK_PIN step will reject this new SHA: the current QPK main QPK_PIN still contains 56a03364d517fd0e2efb2c4d4add8a785fc5e857, so the changed 2dee23c... dependency in pyproject/uv.lock/qsl will be reported as a mismatch and CI will stop before tests. Please either update only after QPK_PIN has advanced to this SHA or keep the repo pinned to the canonical value.
Useful? React with 👍 / 👎.
|
Superseded by the newer QPK pin PR opened after the latest QuantPlatformKit manifest update. |
Summary
2dee23c125c0uv.lock,同步刷新 lockfileTest plan
🤖 Generated with Claude Code