chore(release): bump to 1.0.10; restore version honesty vs published 1.0.9#437
Merged
Conversation
…1.0.9 perseus-ctx 1.0.9 was published to PyPI on 2026-06-20, but the entire Windows-portability sprint (#426–#436), @include windowing (#433), and the scheduler/staleness fixes (#430/#431) all merged on 2026-06-24 — after that wheel. main was therefore labelled 1.0.9 while diverging from the published 1.0.9, the exact version drift the foundation sprint is eliminating. - Bump VERSION / pyproject / server.json → 1.0.10. - Mark CHANGELOG [1.0.9] as released 2026-06-20 with a note that the later work ships in 1.0.10. - Add [1.0.10] section: Windows first-class platform support, and move the genuinely-post-1.0.9 items (#430/#431/#433) out of [1.0.9]. - pyproject: add Microsoft :: Windows and MacOS OS classifiers (now supported). - Regenerate perseus.py (_PERSEUS_VERSION = 1.0.10). Does not publish to PyPI — that remains a manual, credentialed release step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
perseus-ctx1.0.9 was published to PyPI on 2026-06-20, but the entire Windows-portability sprint (#426–#436),@includewindowing (#433), and the scheduler/staleness fixes (#430/#431) all merged on 2026-06-24 — after that wheel. Somainwas labelled1.0.9while its contents diverged from the published1.0.9. That same-number-different-content drift is exactly what the foundation sprint is eliminating.(The original handoff said "PyPI lags at 1.0.7" — that was stale; 1.0.8 and 1.0.9 are both already on PyPI.)
What
VERSION/pyproject.toml/server.json→ 1.0.10.[1.0.9]as released 2026-06-20 with a note that the later work ships in 1.0.10; add a[1.0.10]section for Windows first-class support and move the genuinely-post-1.0.9 items (bug(launchd): installer hardcodes versioned Python path in plists instead of ~/.local/bin/perseus symlink #430/bug(render): stale context.md produces no warning when launchd render job silently calls wrong binary #431/AGENTS.md grows unbounded when @include references a large file #433) into it.pyproject: addMicrosoft :: WindowsandMacOSOS classifiers (now that Windows is first-class and the scheduler supports launchd/cron).perseus.py(_PERSEUS_VERSION = 1.0.10); version pins coherent across all five sources.Not in scope
This does not publish to PyPI — that remains a manual, credentialed release step (no
twine/token in CI or this environment). Once merged,mainis release-ready as 1.0.10 and a publish canpython -m build && twine uploadwhen you choose.🤖 Generated with Claude Code