Repository navigation
The v1.1.0 release notes name the release commit, its digest and the 60 pull requests to it, and leave only the four values the tag gives - #4
Merged
Conversation
…60 pull requests to it, and leave only the four values the tag gives The tag-time pass over lane 3's draft, on Brett Heap's word of 2026-10-28T19:24:31Z as lane 3 relayed it (opensoft/openRepoTools#186 comment 6478511015): lane 2 fills in the placeholders in a spec-leg pull request, lane 4 checks it, and lane 3 merges it. Each value was read offline from opensoft/openRepoTools-code at the release commit, 2a057a6d84e58c8acb4bda20d2b7b667b552c3fe (tree 196299f), or from opensoft/openRepoTools's history. - The release commit is 2a057a6d84e58c8acb4bda20d2b7b667b552c3fe, the code leg's main: the merge of opensoft/openRepoTools-code#1, and the commit the assembly root's `code` gitlink pins at 2a99dd4 (opensoft/openRepoTools#344). It is written in full in the first paragraph and in both `--version` lines that carry it, because `package_version` prints the stamp's COMMIT as it is (openRepoTools:5193-5197) and `stamp_read` holds it to 40 lowercase hex (openRepoTools:749); the repository is the run's GITHUB_REPOSITORY, as the stamp step writes it (release.yml:706). - The digest is 31123e2d08efe36583e72956ed8b8dbbe4b968c75402b59af5b8952be83ef6d5, sorted-ls-tree-r-v1 of that commit's 92 ls-tree records, the gitlink included. release.yml:601-653 computes it with the pinned openRepoShape 190133d's scripts/repo_shape.py `tree_digest`; that function, the copy in tests/test_test_roots.py:126-132 under `python3 -I`, and `git ls-tree -r -z | LC_ALL=C sort -z | tr '\0' '\n' | sha256sum` all give this value. - The count is 60: aaa7bc8..33ce26d on opensoft/openRepoTools's main is 59 commits, none a merge, each subject ending in one distinct pull request number; the legs were carved from 33ce26d, and the code leg then took opensoft/openRepoTools-code#1 (6314fc8, bc7c831, 6c53c9e, 1e6f2d1). The first paragraph's sentence now names both repositories. - The list of other changes is redone over the 60. 51 pull requests had their lines, and the six of opensoft/openRepoTools#228's package series are carried by that issue's lines, as the draft counts them. opensoft/openRepoTools#299 and opensoft/openRepoTools-code#1 now have lines under the triad migration's records, and opensoft/openRepoTools#293 a line of its own at the end of the list, each written from its commit message and diff. The placeholder's line is cut. - opensoft/openBenches#165 is open and has not landed (read 2026-10-28, last updated 2026-10-18), so the one-route paragraph stands. - Checked at the release commit and left as written: the hook pair (openRepoTools:185-188, :2356-2434, :3364-3395 and :3622-3663; the README that says it is now the assembly root's), the openRepoShape pin (contracts/openreposhape-pin.yaml:54 and the upstream/openRepoShape gitlink both name 190133d, openRepoShape's v1.1.0), the milestone's six entries, the CI paragraph (tests.yml:68-75 and its four jobs) and the two release.yml paragraphs (release.yml is the blob 33ce26d had). "Before the tag" marks each item this settles, with its result and the date. The four values only the tag gives, `<release-date>`, `<tag-time>`, `<tag-words>` and `<pypi-url>`, stay as placeholders, with their items, the draft comment and the last line, for the pull request that fills them in. Part of opensoft/openRepoTools#228 and opensoft/openRepoTools#186. Lane: openRepoTools-2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…check of opensoft/openRepoTools#293 gave for the tag-time pass Lane openRepoTools-3's re-check of the notes in opensoft/openRepoTools#293 (comment 6315668503, MERGE AFTER FIXES) left one SHOULD and two NITs, all wording, "for the tag-time pass", and gave each corrected line whole. This commit puts in those two lines byte for byte: - F1, SHOULD, with F2, NIT, in the line on opensoft/openRepoTools#255 and opensoft/openRepoTools#271: "a leg whose directory, or one above it" read as a directory above the leg, which is opensoft/openRepoTools#272's case. The dependency is now unreadable where this account cannot search its directory, or a directory above it inside the leg, the rule of probe_uninitialized's docstring. "One known gap remains" becomes "A known gap remains", since opensoft/openRepoTools#272 holds a second case too. - F3, NIT, in the line on opensoft/openRepoTools#209: "and it stops counting the bash files in prose" had no antecedent, and now reads "and the bash files are no longer counted in prose". Nothing else changes. Part of opensoft/openRepoTools#228 and opensoft/openRepoTools#186. Lane: openRepoTools-2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR updates the v1.1.0 release notes in one file, replacing known placeholders with the release commit, independently computed tree digest, 60-pull-request accounting, and release-time verification results while intentionally retaining the four values that can only be filled after tagging and PyPI publication. Flow diagram for v1.1.0 release-note verificationflowchart LR
Source["Release commit 2a057a6d84e58c8acb4bda20d2b7b667b552c3fe"] --> Digest["Tree digest 31123e2d08efe36583e72956ed8b8dbbe4b968c75402b59af5b8952be83ef6d5"]
Source --> Version["--version output"]
Digest --> Version
Version --> Notes["v1.1.0 release notes"]
Notes --> Remaining["Four post-tag placeholders remain"]
Flow diagram for v1.1.0 pull-request accountingflowchart LR
Previous["v1.0.0 commit aaa7bc8"] --> Main["59 squash commits through 33ce26d"]
Main --> Code["opensoft/openRepoTools-code#1"]
Code --> Release["Release commit 2a057a6d84e58c8acb4bda20d2b7b667b552c3fe"]
Release --> Count["60 pull requests named in the notes"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
…the commit it resolved main to, and that a checkout's ref is still main by default Since the triad split, the documented one-liners fetch the assembly root's front door. Run from stdin, it resolves main once to a commit and runs the implementation with OPENREPOTOOLS_REF set to that commit (root openRepoTools:388-392 at 2a99dd4, and its header at :27-36). The implementation's --version outside a package prints "openRepoTools ($REPO @ $REF)" (openRepoTools:5224 at 2a057a6d), so the one-line install now prints the assembly's repository and a 40-hex commit, where v1.0.0's printed main. A checkout and an installed command still print main, the default of REF (openRepoTools:73), since the assembly's delegate_local sets none. Two lines of the notes said that the one-line install prints main by default, as in v1.0.0: the --version item under "What 1.1.0 adds" and the one-line install's item under "Install and upgrade". Both now say what each route prints. Lane openRepoTools-3, the notes' drafter, asked for this in #4 as its third commit (opensoft/openRepoTools#186 comment 6479087079), with lane 2's wording from comment 6479062441. Part of opensoft/openRepoTools#228 and opensoft/openRepoTools#186. Lane: openRepoTools-2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…RepoTools commit through the assembly root's front door since the triad migration, and cite opensoft/openRepoTools#304 as what the code leg's row-stamp cases are for Two NITs from lane openRepoTools-4's diff-only check of #4 (READY, opensoft/openRepoTools#186 comment 6479419189): - N2. The commit the one-line install's --version now prints is a commit of opensoft/openRepoTools, which the assembly root's front door resolved main to (root openRepoTools:388-392 at 2a99dd4), not the release commit; and the change came with the triad migration, not with opensoft/openRepoTools#228, under whose item the sentence sits. The --version item now says so in lane 4's wording, crediting opensoft/openRepoTools#186, and the one-line install's item under "Install and upgrade" follows it. - N3. In the line on opensoft/openRepoTools-code#1, the parenthetical "(opensoft/openRepoTools#304)" stood just before the line's own pull request and could be read as its source; it now reads "for opensoft/openRepoTools#304". Nothing else changes. Part of opensoft/openRepoTools#228 and opensoft/openRepoTools#186. Lane: openRepoTools-2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
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.
Part of opensoft/openRepoTools#228 and opensoft/openRepoTools#186. This is S16's first step, on Brett Heap's word "a" of 2026-10-28T19:24:31Z, which lane openRepoTools-3 relayed in opensoft/openRepoTools#186 (comment 6478511015):
docs/release-notes/v1.1.0.mdin a spec-leg pull request;--match-head-commit), under Brett Heap's standing word (Releases: annotated tags, release/vX.Y branches, and openrepotools on TestPyPI and PyPI from v1.1.0 openRepoTools#228 comment 6303614082).Four commits change one file,
docs/release-notes/v1.1.0.md(blob1d41db3fbefore), with 20 insertions and 18 deletions:8e4635d, the fill-in:2a057a6d84e58c8acb4bda20d2b7b667b552c3fe. It is the code leg'smain, the merge of The code leg gets its own front door, its standalone checkout context in tests.yml, the assembly root's two length caps and a lane-start row-stamp test that no longer depends on the length of TMPDIR (part of opensoft/openRepoTools#186) openRepoTools-code#1, which the assembly root'scodegitlink pins at2a99dd4. It is written in full in the first paragraph and in the--versionlines, as the package prints it (openRepoTools:5193-5197and:749at that commit).sorted-ls-tree-r-v1,31123e2d08efe36583e72956ed8b8dbbe4b968c75402b59af5b8952be83ef6d5, over 92 records.tree_digest, the suite's copy of it, andgit ls-tree -r -zwith a bytewise sort andsha256sum. Lane 2 ran the last of these again.--versionlines print. Lane 3 posts that run on Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186. Do not merge this pull request until the two agree.aaa7bc8..33ce26don opensoft/openRepoTools'smain, none of them a merge, and then The code leg gets its own front door, its standalone checkout context in tests.yml, the assembly root's two length caps and a lane-start row-stamp test that no longer depends on the length of TMPDIR (part of opensoft/openRepoTools#186) openRepoTools-code#1.190133d, which is openRepoShape's v1.1.0;release.ymlparagraphs.166c110, lane 3's three wording corrections. They come from its re-check of The v1.1.0 notes now say that the fixes for #255 and #280 are part of 1.1.0 and list, by area and from the squash titles of aaa7bc8..a42946e, what else changed on main since v1.0.0 (#228) openRepoTools#293 (comment 6315668503, "For the tag-time pass", which gives each corrected line whole):9211acb, the one-line install's--version, which lane 3 asked for in Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6479087079.mainonce to a commit and runs the implementation withOPENREPOTOOLS_REFset to it (rootopenRepoTools:388-392at2a99dd4).--version(codeopenRepoTools:5224at2a057a6d) prints that commit, where v1.0.0's printedmain. A checkout still printsmainby default (:73).mainby default, as in v1.0.0: the--versionitem and the one-line install's item under "Install and upgrade". Both now say what each route prints.6681d57, two of lane 4's NITs from its READY at9211acb(Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6479419189):opensoft/openRepoToolscommit that the assembly root's front door resolvedmainto, and that came with the triad migration. The--versionitem now says so in lane 4's wording, crediting Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186, and line 122 follows it.Lane 4's check (comment 6479419189) found #4 READY at
9211acb, with no MUST, no SHOULD and six NITs:Left for the second pull request, after PyPI serves 1.1.0:
<release-date>,<tag-time>,<tag-words>and<pypi-url>, which stay as placeholders with their items unticked;2a057a6d…and that the published digest is this one.Checks on the file:
Lane: openRepoTools-2
🤖 Generated with Claude Code