Repository navigation
release 0.6.0: version bump and changelog cut - #66
Merged
Merged
Conversation
Both version strings to 0.6.0, `## [Unreleased]` renamed to `## [0.6.0] - 2026-09-15` with a fresh empty one above it, and the compare links moved on. 23 entries: the corpus-audit fixes (#60), the single-pass record walk (#61), the mapped `PDB.open` and streamed inline-site placement (#62), the C7/C11 signature handling (#65) and the parse-boundary hardening (#53), plus the release workflow itself and three dependency bumps. Minor rather than patch, and deliberately so: the `Fixed` entry for the fused `ChangeCodeLengthAndCodeOffset` annotation says **This moves addresses** -- the second and later ranges of an inline site built from that opcode now start earlier than 0.5.0 reported, on every rust-lld and clang output. `CHANGELOG.md`'s preamble reserves that for a breaking change and requires it to be stated, which that entry does. Verified before tagging: `release_guard.py --tag v0.6.0` extracts the section and reports prerelease=false, and refuses v0.7.0 naming both version strings; 645 passed, ruff and ty clean; `python -m build` plus `twine check --strict` pass on both artefacts; and the wheel, installed into a clean venv and imported with `python -P`, reports 0.6.0 from site-packages with `py.typed` present and runs the `purepdb` entry point. Co-Authored-By: Claude Opus 5 (1M context) <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.
Cuts 0.6.0. Both version strings,
## [Unreleased]renamed to## [0.6.0] - 2026-09-15with a fresh empty one above it, and the compare links moved on. No source changes.This is the first release through
publish-release.yml— the workflow has existed since #59 but no tag has ever exercised it.What is in it
23 entries from five merged PRs plus the release machinery and three dependency bumps:
S_INLINESITE2, separated code, stripped PDBs, MSF block sizes to 32768PDB.openmaps the file; inline sites placed without holding a module's worthWhy minor rather than patch
The
Fixedentry for the fusedChangeCodeLengthAndCodeOffsetannotation says This moves addresses: the second and later ranges of an inline site built from that opcode now start earlier than 0.5.0 reported, on every rust-lld and clang output. The first range, and every single-range site, are unchanged.CHANGELOG.md's preamble reserves exactly this case — "A release that made a previously-resolved address resolve differently would be breaking, and would say so here" — so it is called out in the entry rather than left for a reader to infer.Verified before tagging
release_guard.py --tag v0.6.0extracts the section and reportsprerelease=false;--tag v0.7.0is refused naming both version stringsruff checkandty checkclean on the new pins (ruff 0.16.6, ty 0.0.80)python -m buildandtwine check --strictpass on sdist and wheelpython -Preports0.6.0from site-packages withpy.typedpresent, and thepurepdbentry point runs; metadata readsRequires-Python: >=3.11,License-Expression: BSD-3-ClauseAfter merge
Tag
v0.6.0on the merge commit. The push starts the real run, which parks at thepypienvironment's required reviewer; a manual run from the same tag rehearses to TestPyPI and creates the project there, which is what converts the pending publisher. Approve after the rehearsal looks right.🤖 Generated with Claude Code