chore: align QSL bundle pins#13
Conversation
Co-Authored-By: Codex <noreply@openai.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b349b7ee7
ℹ️ 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 = "quant-platform-kit" | ||
| version = "0.7.40" | ||
| source = { git = "https://github.com/QuantStrategyLab/QuantPlatformKit.git?rev=d18fe32b57a0a8bb746bebf6f11465dd68107eae#d18fe32b57a0a8bb746bebf6f11465dd68107eae" } | ||
| source = { git = "https://github.com/QuantStrategyLab/QuantPlatformKit.git?rev=7032cde4547e7ec59af15df8935d142461a77051#7032cde4547e7ec59af15df8935d142461a77051" } |
There was a problem hiding this comment.
Regenerate the QPK lock entry metadata
This source now points at QuantPlatformKit commit 7032cde..., whose pyproject.toml declares quant-platform-kit version 0.10.0, but the lock entry still records version 0.7.40 and the existing cn-equity-strategies pin still comes from metadata that requires the old d18fe32... QPK URL. Leaving only this URL edited makes the lock graph disagree with the actual package metadata, so a refreshed lock or non-frozen install can silently fall back to the old QPK pin instead of the QSL bundle version. Please regenerate the lock entry from the resolver/update the dependent pin rather than hand-editing just the source URL.
Useful? React with 👍 / 👎.
Co-Authored-By: Codex <noreply@openai.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b16892a8ba
ℹ️ 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".
| version = "0.7.40" | ||
| source = { git = "https://github.com/QuantStrategyLab/QuantPlatformKit.git?rev=d18fe32b57a0a8bb746bebf6f11465dd68107eae#d18fe32b57a0a8bb746bebf6f11465dd68107eae" } | ||
| source = { git = "https://github.com/QuantStrategyLab/QuantPlatformKit.git?rev=37c81901160c5b31127a27dba1c63944933fb6bf#37c81901160c5b31127a27dba1c63944933fb6bf" } |
There was a problem hiding this comment.
Regenerate the QPK lock metadata
Fresh evidence after this new pin: the QPK commit on this line declares quant-platform-kit version 0.10.0 in its pyproject, while this lock entry still records version = "0.7.40". The lock file no longer describes the package being installed, so frozen installs and dependency/version checks can keep treating the bundle as the old QPK release; regenerate this lock entry rather than editing only the git URL.
Useful? React with 👍 / 👎.
|
|
||
| [qsl.compat] | ||
| bundle = "2026.07.1" | ||
| bundle = "2026.07.2" |
There was a problem hiding this comment.
Update the bundle metadata test
With qsl.toml now advertising bundle 2026.07.2, tests/test_qsl_metadata.py:19 still asserts 2026.07.1; I ran python -m pytest tests/test_qsl_metadata.py -q and it fails with that assertion error. Any CI job that includes this metadata test will fail until the expected bundle or this config is updated consistently.
Useful? React with 👍 / 👎.
Co-Authored-By: Codex <noreply@openai.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Summary
Validation