chore(deps): align QPK pin to de18c2e9d93b - #328
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: abd628e060
ℹ️ 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@2381aa4577e9fd6329053a73a1c888929170eaf3", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@de18c2e9d93bcfc2220148a99749447059a6f4c6", |
There was a problem hiding this comment.
In the CI workflow I inspected, the Check QPK pin consistency step runs the QuantPlatformKit guard with --pin-file external/QuantPlatformKit/QPK_PIN; the QPK main pin currently resolves to 2381aa4577e9fd6329053a73a1c888929170eaf3, not de18c2e9d93bcfc2220148a99749447059a6f4c6. With this new dependency SHA, that guard will report the pyproject.toml/uv.lock QPK refs as mismatches and fail before tests, so either keep this dependency at the QPK_PIN SHA or update the upstream QPK_PIN in a coordinated change.
Useful? React with 👍 / 👎.
|
Superseded by #329, which aligns the QPK pin to the current QPK_PIN value. |
1 participant
Summary
de18c2e9d93buv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code