Repository navigation
fix: accept metadata without retired capacity fields - #47
Merged
Merged
Conversation
thestephenromano
marked this pull request as ready for review
November 5, 2026 14:28
Merged
thestephenromano
added a commit
that referenced
this pull request
Nov 5, 2026
Release Please generated this release from merged changes. Its unsigned commit was rejected by the signed-commit rule; the identical tree was signed locally and pushed without changing any generated version or changelog content. ## [0.2.0](v0.1.1...v0.2.0) (2026-11-05) ### ⚠ BREAKING CHANGES * **client:** align Python SDK with API v0.5.0 ([#41](#41)) ### Features * **client:** align Python SDK with API v0.5.0 ([#41](#41)) ([043287a](043287a)) ### Bug Fixes * accept metadata without retired capacity fields ([#47](#47)) ([5547614](5547614)) ### Documentation * adopt strategic pragmatism guidance ([#42](#42)) ([7484eb2](7484eb2)) Companion to API !210. Solver PR #46 remains excluded.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The API's rate-card correction removes
units_chargedandcompute_schedule_versionfrom public responses. Requiring them makes otherwise valid pricing responses fail SDK validation.Accept both fields as optional, deprecated compatibility data for older deployments. Commercial evidence remains exclusively
fcu_quoted/fcu_charged; there is no fallback conversion. Sync and async tests exercise the new response shape. The pinned deployed contract and historical fixtures remain unchanged for this compatibility preparation.Validation: 539 tests passed, 18 opt-in integration tests skipped; Ruff lint/format and mypy passed. GitHub CI passed on Python 3.11 and 3.14, including the Docker notebook check.
Companion to API #155 and API MR !210. Independent of solver PR #46. Draft: coordinate with the API rollout; do not merge/release as part of solver work.