Repository navigation
Release 1.2.0 - #19
Merged
Merged
Conversation
- Version 1.2.0 in pyproject, the package, tests, README, templates, and docs; CHANGELOG cuts [1.2.0] - 2026-09-13; docs/RELEASE_NOTES_v1.2.0.md. - release.yml uses the same memory budgets as the benchmark workflow (aggregate 256 MiB, self 128 MiB); the old 192 MiB flag would have failed the tag build. - RELEASE_DISTRIBUTION and RELEASE_READINESS describe a stable release from a green main commit instead of the never-published rc1. Rehearsed locally: build, twine check, clean-wheel install, benchmark budgets, SBOM, installer syntax, SHA256SUMS. Co-Authored-By: Claude Opus 5 <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
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
Cuts DevDoctor 1.2.0 — the first published release. Version bump everywhere,
CHANGELOGsection,docs/RELEASE_NOTES_v1.2.0.md, release/readiness docs rewritten for a stable tag, andrelease.ymlaligned with the benchmark memory budgets (the hard-coded 192 MiB would have failed the tag build after concurrent probing).After merge: tag
v1.2.0on the merge commit → the release workflow builds, validates, attests, and publishes the GitHub Release with the wheel, sdist,devdoctor-install.sh, SBOM, andSHA256SUMS. PyPI stays off until the Trusted Publisher andpypienvironment exist.Test plan
pytest: 307 passed;ruffclean;devdoctor --version→ 1.2.0v1.2.0🤖 Generated with Claude Code