Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions qsl.toml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
tier = "strategy-library"
ring = 1
tier = "strategy-lib"
upgrade_ring = "ring_b"

[compat]
bundle = "2026.07.2"
bundle = "2026.07.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the QSL bundle pin aligned with package metadata

In environments that consume qsl.toml as the compatibility source, this new 2026.07.3 bundle still resolves quant-platform-kit from the old 37c819... requirement below, while the package metadata and lockfile already resolve 69a025... (pyproject.toml line 13). That makes QSL-resolved runs use a different platform kit than normal installs/CI for the same repository state, so experiments under the advertised bundle are not reproducible with the package dependency set.

Useful? React with 👍 / 👎.

requires = [
"pandas>=2.0",
"quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@37c81901160c5b31127a27dba1c63944933fb6bf",
Expand Down
2 changes: 1 addition & 1 deletion tests/test_qsl_compat_metadata.py
Original file line number Diff line number Diff line change
Expand Up @@ -8,5 +8,5 @@ def test_qsl_compat_metadata_exists_and_bundle() -> None:
with qsl_path.open("rb") as f:
data = tomllib.load(f)

assert data.get("compat", {}).get("bundle") == "2026.07.2", "compat.bundle mismatch"
assert data.get("compat", {}).get("bundle") == "2026.07.3", "compat.bundle mismatch"

Loading