Repository navigation
Switch install docs to PyPI after 2.3.0 - #51
Merged
Merged
Conversation
lineforge 2.3.0 is published on pypi.org as lineforge. Point README, Quick Start, the MCP example, and MIGRATION.md at pip install lineforge, add a PyPI version badge, and document the trusted-publisher release path.
The previous CI run cancelled Test (macos-latest / py3.12) before any steps ran. This empty commit retriggers the suite; no code change.
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
lineforge 2.3.0 is published on pypi.org/project/lineforge under the name
lineforge. This updates the install path from a GitHub URL topip install lineforge.[gui],[dev]) and clone instructions kept for development / the web GUI frontend.docs/release/PYPI_TRUSTED_PUBLISHER.md..github/workflows/release.ymlalready publishes via OIDC trusted publishing (id-token: write,pypienvironment, no API token). Left unchanged.Closes #49.
Acceptance criteria
pip install lineforge; no remaining "not published on PyPI" text for the current package.release.ymlverified as trusted publishing — no long-lived PyPI token required.docs.yml) and CI pass.Out of scope
No code, solver, dependency, version, tag, or release changes. #16 / #41 / #46 are left to their own PRs.