fix(docs): sync version metadata, changelog, and roadmap to shipped reality#4
Merged
Conversation
codex reviewCodex review is not configured for this repository yet. Missing required secret: |
…0/3.2.1 VERSION file lagged at 3.1.0 while pyproject.toml and PyPI (promptpressure-evals) were already at 3.2.1. CHANGELOG had no entries for the two shipped releases: 3.2.0 (pp launcher + PyPI packaging) and 3.2.1 (pp --version fix). reconstructed both from git history.
roadmap claimed v3.0 current and listed already-shipped work as 'next'. rewrote to reflect actual shipped state (3.0/3.1/3.2.x), add a reality-check on the multi-turn vaporware gap, and set v3.3 = drift-corpus + judge-calibration v0.1 as the next release. deprioritized '300+ prompts' (uncalibrated data is noise, not credibility).
StressTestor
force-pushed
the
fix/version-doc-drift
branch
from
4e5eeec to
d23cf73
Compare
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
1 participant
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
the repo docs drifted behind what actually shipped. 3.2.0 and 3.2.1 are both live on PyPI as
promptpressure-evals, butVERSIONstill said 3.1.0, the CHANGELOG had no entries for either release, and the roadmap claimed v3.0 was current and listed already-shipped work as "next". for a project whose whole pitch is becoming a citable, trustworthy eval method, shipping releases with no changelog and a stale version file is an own-goal.what
pplauncher (provider/model/eval-set dropdowns, SSE status, Cancel) + PyPI packaging aspromptpressure-evalspp --versionreads__version__instead of dist metadata.debate/scratch andoutputs/*.zipv3.2.0andv3.2.1git tags on their release commitsnotes
__version__ = 3.2.1.