chore(deps): align QPK pin to 31892425a022 - #93
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: 97a2250cd4
ℹ️ 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".
| dependencies = [ | ||
| "pandas>=2.0", | ||
| "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.
In the CI workflow I inspected (.github/workflows/ci.yml), the Check QPK pin and lock consistency step compares this dependency SHA with external/QuantPlatformKit/QPK_PIN after checking out QuantPlatformKit main unless a same-named QPK branch exists. Current QPK main still advertises QPK_PIN=56a03364d517..., so changing this line and the lockfile to 31892425a022... makes ordinary PR/main CI fail before tests run; keep the consumer pin on the published QPK_PIN or update the upstream pin first.
Useful? React with 👍 / 👎.
1 participant
Summary
31892425a022uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code