Repository navigation
docs(readme): name no latest version in the release note, install note and hosted-server line - #155
Merged
Merged
Conversation
…e and hosted-server line PyPI shows each release's README as its description. The 1.0.0 upload (2026-09-30) carries the README of the v1.0.0 tag, which still said "The latest release is 0.10.4". main now says 1.0.0 is the latest (#154), which the next release would make stale the same way. The release section, the Install note and the hosted-server line now name no latest version; the PyPI release history and the changelog list the releases. The Engine pairing table and the 0.10.4 upgrade notes keep their version-specific rows. Checked: PyPI pineforge-codegen info.version 1.0.0 (uploaded 2026-09-30T04:08Z), tag v1.0.0, VERSION 1.0.0, npm @pineforge/codegen-pyodide latest 1.0.0. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
The note claimed the release section could not go stale, but it still names 1.0.0, and the clone command, its example output, the engine src/source link and "This section describes" also name the release pair. The note now lists them and says why they must change before the tag (PyPI shows the README as it is at the tag). The section also says the changelog covers 1.0.0 on, with earlier notes linked, and that npm has the releases from 0.7.0 on (PyPI also has 0.6.x). Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
…; drop "no engine errors" The release-lane note listed some of the lines that name 1.0.0 as the current release or pair and missed others (the baseline paragraph, the timing note, the engine v1.0.0 mentions near the end). It now asks for every such line, and keeps lines saying what changed in 1.0.0. The opening paragraph said the baseline had "no engine errors"; the engine README at 6b45f510, which gives that baseline's figures, does not state it, so it is dropped. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
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.
Why
PyPI shows each release's README as its package description. The
pineforge-codegen1.0.0 upload (2026-09-30T04:08Z) carries the README of thev1.0.0tag, which still says "The latest release is 0.10.4" and "This installs the latest release, 0.10.4" (checked inhttps://pypi.org/pypi/pineforge-codegen/jsontoday).mainalready names 1.0.0 as the latest (#154), but that sentence goes stale the same way at the next release unless the README is edited before the tag.What changes (README only)
VERSION, which the release workflow writes.pineforge-releaseimage, which ships a released codegen and engine pair; theirengine_infotool reports the image's version" instead of naming the pair. Both servers'engine_inforeport1.0.0today (hosted: checked on mcp.pineforge.dev; the backtest-mcp image v0.9.32 is built on pineforge-release 1.0.0).1.0.0/v1.0.0as the current release or pair (it names the known ones: this section, the baseline paragraph, the enginesrc/source/link, the clone command and its output, "This section describes …", the timing note) and of the "onmain" markers, because PyPI shows the README as it is at the tag; lines saying what changed in 1.0.0 stay. The Install note and the hosted-server line name no version.Unchanged on purpose: the Engine pairing table and the 0.10.4 upgrade notes, which state versioned facts.
Checked against
info.version1.0.0; releases include 1.0.0 and 1.0.0rc1.v1.0.0(GitHub release, 2026-09-30);VERSIONon main:1.0.0.@pineforge/codegen-pyodide:latest1.0.0, versions 0.7.0 to 1.0.0 (its own README, npm/README.md, is not this file); PyPI also has 0.6.5.README only: no Python or C++ changed, so the engine-enabled suite was not run for it; CI (
gate,pytest3.11-3.14) runs on this pull request.When it shows on PyPI
PyPI keeps the 1.0.0 description as uploaded. This README reaches PyPI with the next codegen release, which
release.ymlbuilds frommain.🤖 Generated with Claude Code