chore(deps): align QPK pin to 9bb8f31e898e - #336
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 |
![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: dbb72cd02e
ℹ️ 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@335c7a22bc3f570bd5705427ccc40172eda6b289", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@9bb8f31e898ea238a6446472f9f5e58133128d0c", |
There was a problem hiding this comment.
This dependency pin now points at 9bb8f31e..., but the CI step Check QPK pin consistency checks this file against external/QuantPlatformKit/QPK_PIN; at the QPK revision currently used by CI, that pin file still contains 335c7a22.... As a result, normal CI runs will report this pyproject dependency (and the matching lockfile entries) as mismatched instead of allowing the build to pass; keep the consumer pin at the QPK_PIN value until the canonical pin advances.
Useful? React with 👍 / 👎.
|
Superseded by the current QPK manifest target fdae6666ba4e; the matching replacement PR remains open. |
1 participant
Summary
9bb8f31e898euv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code