Repository navigation
docs: identify released migration inputs and consumer boundaries - #138
Merged
Merged
Conversation
Correct stale unreleased wording for Data 0.3.0, link release examples, and distinguish historical integration checks from released Data availability. Keep Diagnostic analytics and Backtest runtime/account responsibilities explicit. Closes #137
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.
Closes #137.
The published migration guide still describes Data 0.3.0 APIs as unreleased and recommends an older Engineer development checkout. Identify the released APIs, link the immutable release examples, and provide the Data input handoffs for Diagnostic and Backtest. Keep prior cross-library checks explicitly historical and preserve all adjustment, missing-data and runtime/account boundaries.
Documentation only: no package API, dependency, numerical definition or runtime behavior changes.
Verification at 2eb2e62:
The live guide is still the 0.3.0 deployment. This PR prepares its correction; it does not deploy documentation or publish a package. Merge ordering must preserve the currently qualified release source until its release-security decision is resolved.
AI assistance: Codex reproduced the live-documentation mismatch, edited this guide and executed the listed verification. Maintainer-directed review covers every changed statement; historical consumer evidence has not been promoted into a new compatibility claim.