chore(deps): align QPK pin to 31892425a022#325
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: c37224be7f
ℹ️ 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", | ||
| "longport==3.0.23", | ||
| "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.
Use the QPK_PIN value for the dependency pin
In the CI path I checked (.github/workflows/ci.yml lines 87-92), the pin guard runs against external/QuantPlatformKit/QPK_PIN and compares QuantPlatformKit.git@... entries to that file's contents, not to the checked-out repository commit. At the referenced 31892425... commit, QPK_PIN contains 618b786d27351dc9ec186f27d01f7da39c6dcf81, so this pyproject.toml entry will be rejected by the mandatory pin-consistency check before CI can complete; pin to the QPK_PIN value and refresh the lockfile instead.
Useful? React with 👍 / 👎.
Summary
31892425a022uv.lock,同步刷新 lockfileTest plan
🤖 Generated with Claude Code