chore(deps): align QPK pin to 230854059c11 - #372
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: b99e8fc344
ℹ️ 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@b371322b948e4298920a7d8613b155245dcd5f8d", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@230854059c11a3711fed4bd997e3f8a7f37cba32", |
There was a problem hiding this comment.
This QPK SHA publishes a newer QSL pin bundle for the strategy packages (qsl-pins.txt points UsEquityStrategies at 2438d6b... and HkEquityStrategies at bf4c748...), but this commit leaves this repo on 17ddb86.../b6a8ac... in pyproject.toml, qsl.toml, and uv.lock. Because the production Docker build runs uv sync --frozen --no-dev, Cloud Run will deploy the new shared contracts with older strategy libraries rather than the bundle QPK published, so runtime behavior can miss the matching strategy-side compatibility/risk-gate changes. Please update the strategy pins and lockfile together with the QPK bump.
Useful? React with 👍 / 👎.
1 participant
Summary
230854059c11uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code