Skip to content

fix: sync version metadata and remove stale legacy README API#32

Open
dev3Nigerian wants to merge 2 commits intotempoxyz:mainfrom
dev3Nigerian:fix/sync-version-and-readme-api
Open

fix: sync version metadata and remove stale legacy README API#32
dev3Nigerian wants to merge 2 commits intotempoxyz:mainfrom
dev3Nigerian:fix/sync-version-and-readme-api

Conversation

@dev3Nigerian
Copy link
Copy Markdown

@dev3Nigerian dev3Nigerian commented Mar 6, 2026

Summary

  • sync pytempo.__version__ with pyproject.toml (0.3.1)
  • make Sphinx release derive from pytempo.__version__ to avoid future drift
  • remove stale README references to removed legacy APIs (create_tempo_transaction, patch_web3_for_tempo)
  • update README examples list to match files that actually exist in examples/
  • add tests/test_version.py regression tests for package/docs version consistency
  • refresh uv.lock metadata so the editable pytempo package entry tracks 0.3.1

Problems Solved

  • package runtime version was stale (0.3.0) while project metadata was 0.3.1
  • docs release string was hardcoded to the stale version
  • README instructed users to import APIs that were removed in v0.3.0
  • lock metadata still pointed at an older editable package version

Verification

  • uv run ruff check .
  • uv run ruff format --check .
  • uv run pytest -q (84 passed, 23 skipped)

Tradeoffs / Open Questions

  • README now only documents the typed API and explicitly notes legacy API removal; no compatibility shim was reintroduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant