chore(deps): align QPK pin to 31892425a022 - #265
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: ef93e6ed7a
ℹ️ 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-auth", | ||
| "numpy", | ||
| "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.
When CI checks out QuantPlatformKit main (the default in .github/workflows/ci.yml unless a same-named QPK branch exists), the Check QPK pin consistency step runs the external checker against external/QuantPlatformKit/QPK_PIN and compares this dependency line plus the lockfile entries to that canonical pin. I checked the current QPK main pin and it still resolves to 56a03364d517..., so changing the consumer repo to 31892425a022... makes that CI step report a mismatch before the PR can merge; wait for the QPK_PIN source to advance or pin to the SHA recorded there.
Useful? React with 👍 / 👎.
1 participant
Summary
31892425a022uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code