[brettheap]

Part of opensoft/openRepoTools#228 and opensoft/openRepoTools#186. This is the second of S16's two notes pull requests, as lane openRepoTools-3 set them out in opensoft/openRepoTools#186 comment 6478511015, on Brett Heap's word "a" of 2026-10-28T19:24:31Z:

• once PyPI serves 1.1.0, lane openRepoTools-2 fills in the four values only the tag gives and cuts the draft's scaffolding;
• lane openRepoTools-4 checks it diff-only;
• lane openRepoTools-3 merges it by S10's rules (a merge commit, green, --match-head-commit), and then creates the GitHub Release from the merged file, on Brett Heap's word relayed in Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6481136882.

One commit changes one file, docs/release-notes/v1.1.0.md, from blob 08c4d436 (the merge of #4), 147 lines, to 130 lines:

• The four values:
  • <release-date> is 2026-10-28, the tag's UTC date.
  • <tag-time> and <tag-words> are 2026-10-28T21:14:02Z and "yes, tag v1.1.0 at 2a057a6d and dispatch it", as the tag message gives them. The "Tagged on" line equals the message's own line byte for byte. It is plain text, as v1.0.0.md's is.
  • <pypi-url> is https://pypi.org/project/openrepotools/1.1.0/, written as an autolink, as the milestone's is.
• N1, from lane 4's check of 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 (Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6479419189): aaa7bc8..main on opensoft/openRepoTools also counts 60, by a different set. The first paragraph now says that the split, Adopt the three-repository shape: openRepoTools-spec and openRepoTools-code openRepoTools#344, landed there after the 60 and is not one of them.
• N5: the package series of Releases: annotated tags, release/vX.Y branches, and openrepotools on TestPyPI and PyPI from v1.1.0 openRepoTools#228 is six pull requests that only the checklist named. "Full list" now names them, so each of the 60 is named in the notes.
• The cuts: the draft comment and the "Before the tag" section.
• The last line: lane 3's wording, a link to this file, as Design Decision 11 asks (Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6478721229).

What lane 2 read, after the tag:

• The tag (N6):
  • git ls-remote on opensoft/openRepoTools-code reads refs/tags/v1.1.0 as the annotated tag 36d8d5141419d89741fa343b71ddcd1412baf4d9.
  • Its peeled ^{} is 2a057a6d84e58c8acb4bda20d2b7b667b552c3fe, the release commit, and that is still the code leg's main.
  • The tag message's sha256 is b378853f68a316a46a1cb4b01bc276b6bded0b0ad9010e78a153e190e04fe827, as lane 3 gives it in Triad migration (feature 004-migrate-to-triad): execution tracking under Brett Heap's word of 2026-10-07 openRepoTools#186 comment 6480977080.
• The release run: run 40770351691 on v1.1.0, at 2a057a6d. All six of its jobs succeeded, and publish to PyPI finished at 21:26:49Z.
• The published digest (N6):
  • The index: PyPI serves openrepotools 1.1.0. Its JSON and its page both answered 200 at 21:27:53Z. It holds one file, openrepotools-1.1.0-py3-none-any.whl, sha256 9d01aa6360d844b906c806087e7f8a3de0e8d51c99dc7ec1ff42f39b87411795, the same file TestPyPI holds.
  • The stamp: that wheel's openrepotools/_release.py, read without running it, holds VERSION 1.1.0, TAG v1.1.0, COMMIT 2a057a6d84e58c8acb4bda20d2b7b667b552c3fe, DIGEST 31123e2d08efe36583e72956ed8b8dbbe4b968c75402b59af5b8952be83ef6d5 and REPOSITORY opensoft/openRepoTools-code.
  • The install checks: each of the three printed five --version lines equal to the notes' five.
• The recount (N1):
  • The root: aaa7bc8..33ce26d on opensoft/openRepoTools's main holds 59 commits. None is a merge, and each has its own pull request number. They are the same 59 as the mapping on 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.
  • The code leg: after the carve, its one merge is 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, and its main is still the release commit.
  • So the 60 stands. aaa7bc8..2a99dd4 also counts 60 because Adopt the three-repository shape: openRepoTools-spec and openRepoTools-code openRepoTools#344 is one of its commits, and 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 is not.
• setup-estate-commands.sh: accept pipx's openRepoTools link, as openRepoTools --install will (opensoft/openRepoTools#228) openBenches#165, read at 21:25:42Z:
  • It is an open issue, last updated 2026-10-18, and nothing in workBenches references it.
  • scripts/setup-estate-commands.sh on workBenches' main still refuses a symlinked openRepoTools (:387-388 and :494-501). Its one change since 2026-10-18, ff60b17e, changed only its comments and its file list.
  • So the one-route paragraph stands as written.

Lane: openRepoTools-2

🤖 Generated with Claude Code

Summary by Sourcery

Finalize the v1.1.0 release notes for publication with verified tag and PyPI information, corrected release accounting, and the draft material removed.

Enhancements:

• Finalize the v1.1.0 release notes with the tag metadata, PyPI link, pull-request count, and complete package-series listing.
• Remove draft placeholders, scaffolding, and checklist content from the release notes.

Documentation:

• Update the v1.1.0 release notes with verified release and publication details and link to the canonical notes file.

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 21 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Finalizes the v1.1.0 release notes by incorporating verified tag and PyPI details, documenting the split and package-series accounting, and removing temporary draft scaffolding before release publication.

Flow diagram for finalizing v1.1.0 release notes

flowchart LR
    Tag["v1.1.0 annotated tag"] --> Notes["Update release notes"]
    PyPI["PyPI 1.1.0 publication"] --> Notes
    Notes --> Verified["Verified release details"]
    Notes --> Accounting["60-PR count and package series"]
    Notes --> Final["Final notes without draft scaffolding"]

Loading

File-Level Changes

Change	Details	Files
Finalize the v1.1.0 release notes with tag and PyPI metadata, while removing draft-only scaffolding.	Replace placeholders with the tag date, timestamp/message, and PyPI release URL. Remove the draft comment, checklist, and pre-tag instructions. Add the final link identifying the notes file used for the release.	docs/release-notes/v1.1.0.md
Clarify the release's pull-request accounting and package-series coverage.	Explain that the repository split landed after the 60 counted pull requests. Name all six pull requests in the package series for issue #228. Retain the finalized 60-PR recount and release/code-leg references.	docs/release-notes/v1.1.0.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.