Conversation
All milestones (M0–M13) are complete. Bump package version, update install instructions to use PyPI, and consolidate CHANGELOG under the v1.0.0 heading. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Pull request overview
Prepares the leadforge package for a stable v1.0.0 release by updating versioning metadata and release-facing documentation.
Changes:
- Bump version to
1.0.0in both packaging metadata and runtime__version__. - Update project maturity classifier to
Production/Stable. - Refresh public docs for PyPI installation and consolidate the changelog into a v1.0.0 release entry with collapsed milestone history.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| pyproject.toml | Updates package version to 1.0.0 and marks the project as Production/Stable. |
| leadforge/version.py | Updates runtime __version__ to 1.0.0 (used by imports/CLI). |
| README.md | Switches install instructions to pip install leadforge and removes “PyPI coming” note. |
| CHANGELOG.md | Replaces “Unreleased” with a dated v1.0.0 release section and collapses milestone history. |
| .agent-plan.md | Updates internal tracker to reflect the v1.0.0 release and checklist completion. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Single version source: version.py now reads from importlib.metadata instead of duplicating the literal from pyproject.toml. - README: add git+ install fallback since PyPI publish is a separate step. - CHANGELOG: remove stray parens from date, add empty Unreleased section per Keep a Changelog convention. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
pr-agent-context report: No unresolved review comments, failing checks, or actionable patch coverage gaps were found on PR #47 in repository https://github.com/leadforge-dev/leadforge. Treat this PR as all clear unless new signals appear.Run metadata: |
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.
Summary
0.1.0to1.0.0inpyproject.tomlandleadforge/version.pypyproject.tomlclassifier fromPre-AlphatoProduction/StableREADME.mdinstall instructions:pip install leadforge(waspip install git+...); remove "PyPI coming" noteCHANGELOG.md: renameUnreleasedtov1.0.0 — (2026-05-02), add highlights section, fold milestone headings into collapsible development historyTest plan
pytestpasses (no code changes)python -c "import leadforge; print(leadforge.__version__)"prints1.0.0🤖 Generated with Claude Code