This repository was archived by the owner on Nov 12, 2026. It is now read-only.
Repository navigation
chore: archive notice and v1.9.1 final release - #54
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Final release before archiving. The legacy Fitbit Web API + OAuth 2.0 endpoints were decommissioned on 2026-10-30 (#53), so the tool cannot work. This makes that visible on PyPI, where people still land.
No code changes — the API returns a decommissioned error on its own, so a runtime banner would only add noise.
Evidence
Development Status: 5 - Production/Stable.After: archival notice + alternative,
Development Status: 7 - Inactive(oncev1.9.1is released).black --check/isort --check-only: clean, 11 files unchanged. Tests not run — no.pylogic touched, only a version string.Merge Danger
Door: two-way — README and classifiers are cosmetic; the version bump is only consumed by the next release tag.
Blast Radius: docs-only, plus one permanent PyPI version number.
After merge: tag
v1.9.1→ GitHub Release (publishes to PyPI) → archive the repo.