chore(deps): align QPK pin to f0d6bc739943 - #329
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: b2230d94c0
ℹ️ 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@f0d6bc7399433b9a1ccdaab1f0874faf184cfa84", |
There was a problem hiding this comment.
Pin QPK to the canonical QPK_PIN SHA
This updates the dependency to the QPK repository commit f0d6bc..., but that checkout's QPK_PIN points to de18c2e9d93bcfc2220148a99749447059a6f4c6. I checked the CI path in .github/workflows/ci.yml:113-118: it runs external/QuantPlatformKit/scripts/check_qpk_pin_consistency.py --pin-file external/QuantPlatformKit/QPK_PIN, so this line, the override, and uv.lock will be reported as mismatches and the PR will stay red until they use the QPK_PIN SHA instead of the sync commit SHA.
Useful? React with 👍 / 👎.
|
Superseded: downstream pin sync must update qsl.toml compatibility metadata together with pyproject.toml and uv.lock. |
Summary
f0d6bc739943uv.lock,同步刷新 lockfileTest plan
🤖 Generated with Claude Code