Skip to content

chore(qsl): adopt compatibility bundle 2026.07.4 #332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pigbibi merged 1 commit into from
Jul 11, 2026
Merged

chore(qsl): adopt compatibility bundle 2026.07.4 #332

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion qsl.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ us_equity_strategies = "17ddb86c72d44b2c7b78ba7a10d8f71b21180166"
hk_equity_strategies = "b6a8ac2ad3c8110b5ea74fb059c8206388d63bcd"

[qsl.compat]
bundle = "2026.07.3"
bundle = "2026.07.4"

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Update the bundle assertion with this metadata bump

Changing the bundle to 2026.07.4 leaves the checked-in metadata test expecting 2026.07.3 in tests/test_qsl_metadata.py:17; I ran python -m pytest tests/test_qsl_metadata.py -q and it fails with this exact mismatch. Any CI workflow that runs the test suite will reject this metadata-only change until the assertion is updated or made to follow the new bundle value.

Useful? React with 👍 / 👎.

Loading