chore(deps): align QPK pin to 56a03364d517 - #331
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: 78886529cb
ℹ️ 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@56a03364d517fd0e2efb2c4d4add8a785fc5e857", |
There was a problem hiding this comment.
In the normal CI path I inspected (.github/workflows/ci.yml lines 113-118), the QPK checkout supplies external/QuantPlatformKit/QPK_PIN to check_qpk_pin_consistency.py; the current QPK main pin is de18c2e9d93bcfc2220148a99749447059a6f4c6, so this newly declared 56a03364d517... ref will be reported as a mismatch in pyproject.toml (and the matching uv.lock entries) whenever CI resolves QuantPlatformKit to main, including pushes to main and PRs without a same-named QPK branch. Please update these dependency refs/lockfile to the QPK_PIN value or update the pin source in lockstep.
Useful? React with 👍 / 👎.
1 participant
Summary
56a03364d517uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code