chore(deps): align QPK pin to 2381aa4577e9 - #327
Conversation
Automated downstream QPK pin update after QPK_PIN landed on main. Co-Authored-By: Claude <noreply@anthropic.com>
![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: 7004cef1fe
ℹ️ 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".
🤖 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: d194ee64f9
ℹ️ 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@69a0256934d081b5ef309a885384b9eb9f62cf90", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@2381aa4577e9fd6329053a73a1c888929170eaf3", |
There was a problem hiding this comment.
Updating the installed QPK commit here leaves the repository metadata inconsistent: qsl.toml still declares [qsl.requires].quant_platform_kit = "69a0256934d081b5ef309a885384b9eb9f62cf90" while pyproject.toml and uv.lock now install 2381aa4577e9fd6329053a73a1c888929170eaf3. Any QSL metadata/upgrade tooling that reads qsl.toml will report or propagate the old runtime requirement even though the package resolver uses the new one, so the same pin bump should update that metadata as well.
Useful? React with 👍 / 👎.
1 participant
Summary
2381aa4577e9uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code