release: v1.0.0 — Stable#133
Merged
Merged
Conversation
selectools 1.0. The public API is frozen; @stable symbols carry a 2-minor removal promise. Development Status -> Production/Stable. - Version 0.29.0 -> 1.0.0; classifier 4 - Beta -> 5 - Production/Stable - CHANGELOG [1.0.0] milestone entry (folds in the stability promotions from 0.29.0 + the Python 3.9 drop); docs/CHANGELOG synced - README 'What's New in v1.0' + corrected the stale stability-marker example (AgentGraph/patterns are now @stable) - MIGRATION_1.0 finalized (removed the 'provisional until tag' note; reconciled the promoted/held lists with the actual 0.29.0 promotions) - Version stamps -> 1.0.0; llms-full regenerated; Protocol-workaround comments 3.9-3.11 -> 3.10-3.11 across src (post-3.9-drop) The 3.9 drop folds into 1.0 per John (no interim 0.30.0). Verified: ruff + mypy clean.
Asserted __version__.startswith('0.') — stale at 1.0.0. Now checks a valid semver pattern (works for 0.x, 1.x, and beyond).
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.
selectools 1.0. The public API is frozen;
@stablesymbols now carry a compatibility promise (no removal / breaking signature change without a ≥2-minor deprecation cycle).Development Status :: 5 - Production/Stable.Folds the [Unreleased] work into 1.0 per the call to skip an interim 0.30.0: the stability promotions shipped in 0.29.0, and the Python 3.9 drop (merged in #132) lands here as the one breaking change since 0.29.0.
Changes
0.29.0→1.0.0; classifier4 - Beta→5 - Production/Stable[1.0.0]milestone entry + docs mirror synced@stablenow, not beta)MIGRATION_1.0.mdfinalized — removed the "provisional until tag" note; reconciled the promoted/held lists with the actual 0.29.0 promotions (toolbox tools, module promises,SessionSearchResult,PlanningConfig);planningis no longer in the "not promoted" listllms-full.txtregenerated; Protocol-workaround comments3.9-3.11→3.10-3.11across src (post-drop)What "stable" covers
Agent loop + config, providers, tools + the mature toolbox, sessions, memory, guardrails, orchestration graphs, the pattern agents, the policy layer, core types. Still
@beta(free to evolve in 1.x): RAG/embeddings, MCP, A2A, the evaluator catalog, unified memory, the scheduler, the newest backends.scripts/stability_audit.pyis the live map.Verification