Skip to content

chore: prepare v0.1.0 for release - #4

Merged
ejames-dev merged 1 commit into
mainfrom
release/v0.1.0
Oct 3, 2026
Merged

ejames-dev merged 1 commit into
mainfrom
release/v0.1.0

Conversation

@ejames-dev

Copy link
Copy Markdown
Owner

Summary

  • Prepare package version 0.1.0 and update the lockfile without changing dependency pins.
  • Add the user-selected MIT license and modern package license metadata; raise the Setuptools build minimum to 77.0.3 for that metadata.
  • Add release notes and an evidence-backed release-readiness checklist.
  • Include license/changelog/lockfile/checklist in source archives and add installed-wheel CI checks on Python 3.11–3.13.
  • Link the newly published user wiki and add package project URLs.

Scope and safety

  • Runtime code, tests, and runtime dependencies are unchanged.
  • Existing offline, evidence-interpretation, and non-overwrite boundaries remain intact.
  • This PR does not create a tag, GitHub release, or PyPI publication. Those require separate approval.
  • The repository description was separately corrected to reflect inspection, comparison, and reporting.

Verification

  • 50 unittest tests pass on Python 3.11, 3.12, and 3.13.
  • Pytest: 50 tests and 125 subtests pass. Ruff format/lint pass.
  • Wheel and source archive build with version 0.1.0 and the MIT license.
  • Archive contents include required docs/examples/tests/lock and exclude private data directories.
  • Extracted source archive installs with the lockfile and passes all 50 tests.
  • Installed wheel outside checkout passes help, invalid-argument, inspect, compare, no-change, report-byte, timeout, and existing-note protection checks.
  • Installed-code comparison passes with network entry points disabled.
  • Exact new CI shell step passes locally. Installed environment passes uv pip check.
  • pip-audit/PyPI reports no known vulnerabilities in the seven checked locked Linux runtime/dev dependencies; no fixes applied.
  • Self-review complete; independent reviewer tools unavailable. This is not a comprehensive independent security audit.

Next gate

Review and merge this preparation PR, verify post-merge CI, then explicitly approve the signed release tag and publication destination. Rebuild artifacts from the final approved release commit.

Add the user-selected MIT license, version and package metadata, release notes, and a release-readiness checklist. Verify installed wheels in CI and link the public wiki. Keep runtime behavior unchanged; tagging and publication remain separate approval steps.
@ejames-dev
ejames-dev merged commit 1ef462f into main Oct 3, 2026
6 checks passed
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