chore(qsl): phase2 compat 2026.07.1 + dependency refs#44
Conversation
Co-Authored-By: Codex <noreply@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 57405523ac
ℹ️ 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".
| name = "hk-equity-strategies" | ||
| version = "0.4.7" | ||
| source = { git = "https://github.com/QuantStrategyLab/HkEquityStrategies.git?rev=dbbefb688cd144837aa59581b1930a14c11411ad#dbbefb688cd144837aa59581b1930a14c11411ad" } | ||
| source = { git = "https://github.com/QuantStrategyLab/HkEquityStrategies.git?rev=00dd0e5b62a6fa65bd9262e15c083468e8b8c191#00dd0e5b62a6fa65bd9262e15c083468e8b8c191" } |
There was a problem hiding this comment.
Refresh the transitive QuantPlatformKit lock entry
When this locked hk-equity-strategies ref is used via uv sync --locked or similar lockfile-based installs, the environment still gets the old quant-platform-kit ref because this commit updates only the strategy package entry while leaving the quant-platform-kit package source at dfdbef6... later in uv.lock. The pinned 00dd0e5... strategy ref declares quant-platform-kit @ ...0063af3..., so the lockfile no longer represents the dependency set from the selected strategy commit and can run against a stale platform-kit implementation.
Useful? React with 👍 / 👎.
Summary
Validation