Repository navigation
Prepare v0.2.0: interactive charts and current release guidance - #27
Merged
Merged
Conversation
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.
Prepare v0.2.0 so the tagged install includes the interactive chart tooling and PNG improvements already merged into main. Align the package/lock version, README, changelog, wheel example and release checklist; add a compact compatibility index that keeps native observations, user reports and browser harness results distinct.
This candidate is based on merged PR #26. Release notes include its private-key delivery clarification, and a one-word probe-report correction avoids implying the proposed Muse adapter exists. That adapter remains unimplemented. Source-package inspection found the local Node harness dependencies being included by the build backend despite their nested Git ignore rule. An explicit sdist exclusion now removes that development directory while retaining its manifests/test sources and all runtime assets. Dependency versions, archive schema, metric definitions, collector and schedulers are unchanged. Historical v0.1.0 notes and the approved real screenshots/wordmark are preserved.
Verification on 7225035:
Merge requires all three OS checks for this final head. After merge, require the exact main package smoke before tagging v0.2.0 and publishing clean wheel/sdist/SHA256SUMS assets. Existing v0.1.0 tag/assets remain immutable. No PyPI upload, hosted site, live Garmin request or new native acceptance test is part of this preparation.