chore(deps): align QPK pin to f07f0bdeb658#322
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 |
|
Superseded: QPK downstream sync is being corrected to update both supported qsl.toml pin layouts. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3bbda3fc3d
ℹ️ 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@2381aa4577e9fd6329053a73a1c888929170eaf3", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@f07f0bdeb6580e1f28109830ccde85cb8ace092a", |
There was a problem hiding this comment.
Changing the install pin here without updating qsl.toml leaves the repository metadata advertising the old QPK commit (2381aa...) while pyproject.toml installs f07f0.... This is already enforced by tests/test_qsl_metadata.py, which compares qsl.requires.quant_platform_kit with this dependency pin, so CI fails immediately and any metadata-driven bundle checks will see the wrong platform revision.
Useful? React with 👍 / 👎.
| "google-auth", | ||
| "longport==3.0.23", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@2381aa4577e9fd6329053a73a1c888929170eaf3", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@f07f0bdeb6580e1f28109830ccde85cb8ace092a", |
There was a problem hiding this comment.
The Check QPK pin consistency workflow reads external/QuantPlatformKit/QPK_PIN; that file is the compatibility SHA, not necessarily the QuantPlatformKit repo commit SHA (for example, at f07f0..., QPK_PIN contains f0d6bc...). Pinning this dependency to f07f0... therefore makes the blocking guard reject pyproject.toml/uv.lock even after the local metadata mismatch is fixed.
Useful? React with 👍 / 👎.
Summary
f07f0bdeb658uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code