Repository navigation
docs(release): v0.3.0 changelog fold, upgrade notes and release checklist (ITL-873) - #329
Conversation
…(ITL-873) Assemble the changelog fragments into [0.3.0], add the SemiJoin fragment (ITL-847), add the upgrade notes, the v0.3 release checklist and the data context freeze step. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
ITL-873 Cut the Orcapod Python v0.3.0 release
OverviewFinal step of the v0.3 release project. Once every issue committed to milestones 1 to 3 is merged or explicitly moved out, prepare the release notes and mark the release commit with the tag Goals & Success Criteria
Scope & BoundariesIn scope:
Out of scope:
Dependencies & Risks
|
Restore CHANGELOG.md and changelog.d/ to main's state (the earlier fold was stale). Keep the install text in README.md and docs/index.md and the freeze step in RELEASING.md, reconciled with main. Replace the 2026-11-12 checklist with a 2026-11-15 one and add the upgrade notes draft, to be inserted at the fold. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s (ITL-873) Side-effect deliveries repeat after clear_cache(), not through a job.run() argument. Add a note for users coming from 0.1.4 and link the README to the section's anchor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
CodeRabbit CLI review, run 1 —
Run 2 is on Posted by a Claude Code agent on behalf of @eywalker. |
…th bindings.store (ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
CodeRabbit CLI review, run 2 —
Run 3 is on Posted by a Claude Code agent on behalf of @eywalker. |
|
CodeRabbit CLI review, run 3: This head does not include the data context freeze commit. It is held locally for the developer's approval and will be reviewed when it is added. Posted by a Claude Code agent on behalf of @eywalker. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…order (ITL-873) Upgrade notes: ITL-1147, ITL-611 set container, ITL-1150, PLT-4864 and an ITL-946 placeholder. Checklist: fragment PRs done; remaining order ITL-946, fold, freeze as the last commit, tag; v* tag protection precondition. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…TL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
CodeRabbit CLI review (
A new run on the fixed head follows. Posted by a Claude Code agent on behalf of @eywalker. |
|
CodeRabbit CLI review (
No code change, so no new head; the next CLI run is on the phase B head. Posted by a Claude Code agent on behalf of @eywalker. |
…ories (ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ITL-873) RELEASING.md takes main's golden-history release step in place of the branch's old freeze step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… ITL-1154 before the fold (ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
CodeRabbit CLI review ( No findings. The earlier declined finding ( Posted by a Claude Code agent on behalf of @eywalker. |
…(ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….3.0 release branch (ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-873) Lines from the fragments merged today: the v1 hash definition (development builds discarded, side effects delivered again, source id forms, record_id_columns, text record ids), map_tags / map_data strictness and keyword-only options, and connector databases refusing function nodes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…C (ITL-873) generate_golden_hashes.py --release dates the release revision with the local clock, so RELEASING.md and the golden-hashes reference run it with TZ=UTC and check the date against the CHANGELOG heading. The checklist records today's merges, the fold reorder (option A) and the dating commit before the freeze. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… branch (ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he v0.3.0 release branch (ITL-873) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> # Conflicts: # RELEASING.md
assemble_changelog.py --version 0.3.0 folds the 90 fragments into [0.3.0] and deletes them. The upgrade notes (#### Upgrading from 0.2.0) open Breaking changes and migration; their draft is deleted. Each bullets-only fragment block that had landed under an earlier fragment's #### heading is moved, text unchanged, directly under its category (Breaking: under a new #### Other breaking changes). The heading stays 'unreleased' until the dating commit before the freeze. RELEASING.md names docs/dev/plans/ for the release checklists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ry (ITL-873) (#413) * docs(release): date the v0.3.0 changelog heading 2026-11-17 (ITL-873) The release date is the UTC day of the tag. #329 merged with the fold but without its last two commits; this follow-up PR carries them, the freeze last. The checklist records it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(release): record v0.3.0 in the golden history of data context v1 (ITL-873) TZ=UTC uv run python tests/test_hashing/golden/generate_golden_hashes.py --release 0.3.0 Appends the release revision (release 0.3.0, date 2026-11-17, added {}) to the golden history of std:v1:default, sets released_in, and pins the revision digest and the manifest digest in released_manifests.json. No golden file changes. From now on a released golden value changes only with a new data context version. Approved by the developer on 2026-11-17. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Edgar Y. Walker <> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…al tags slice (ITL-1023) Clean merge: README rewrite (#412), changelog fold (#329), v0.3.0 date and golden release record (#413). Data context v1 is frozen as release 0.3.0; the golden folder and src/orcapod/contexts are byte-identical to main. The slice's changelog fragments (ITL-1017, ITL-1019, ITL-1022, ITL-1023) stay fragments for the next release. Refs ITL-1023 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs ITL-873
Release PR for v0.3.0. Two commits are still to come, after review and the developer's approval: the dating commit, then the freeze as the LAST commit (see the end). Do not merge before them.
What the release contains (head refreshed 2026-11-17 against
main62899bd)Every v0.3.0 pull request has merged into
main(the last: #406 ITL-1154, #409 ITL-1160, #408 ITL-1162, #410 and #411 ITL-1169), andmainis merged into this branch (merges only, no rebase or force-push).CHANGELOG.md: the 90changelog.d/fragments are folded into## [0.3.0]byuv run python scripts/assemble_changelog.py --version 0.3.0, which deleted them (changelog.d/keeps onlyREADME.md). The heading stays## [0.3.0] — unreleaseduntil the dating commit.#### Upgrading from 0.2.0opens Breaking changes and migration. It is a grouped list of every change a0.2.0(or0.1.4) user meets, each with what to do and its issue: stored data (nothing written by 0.2.0 or a development build of v0.3 is reused; side effects of a development build are delivered again), requirements, renamed or removed names, running a job, operators, function pods, sources and binding, values refused now, extension authors, documentation. Its draft (docs/dev/plans/2026-11-15-v0.3-upgrade-notes-draft.md) is deleted in the same commit.####heading and read as part of it. Each is moved, text unchanged, directly under its category, before the first####entry; in Breaking changes and migration: the upgrade notes, then the moved bullets under a new#### Other breaking changes, then the detailed entries.scripts/assemble_changelog.pyis not changed here; fixing its order is a separate issue after the tag.docs/dev/plans/2026-11-15-v0.3-release-checklist.md: the v0.3.0 instance ofRELEASING.md: steps with who and status, the PRs that landed, the pre-push checklist, and thenauticalabfast-forward push and Release workflow as the developer's steps.RELEASING.md: as onmain, plus: release dates are UTC days, and the freeze runs withTZ=UTC(the script dates the release revision with the local clock); the per-release checklists are indocs/dev/plans/.docs/reference/golden-hashes.mdshows the sameTZ=UTCcommand.README.md,docs/index.md: install text (0.3.0is the first PyPI release since0.1.4; tables written by0.2.0are not read; see Upgrading from 0.2.0). README links are absolute so they resolve on PyPI.Checks
On
095aca3e:pytest tests/test_docs tests/test_changelog_fragments.py tests/test_design_issues.py tests/test_contexts: 190 passed;assemble_changelog.py --check: OK;generate_golden_hashes.py --check: golden values of semantic, schema, arrow, datagram, pipeline, torch match;ruff checkandruff format --checkclean;basedpyright0 errors (exit 0). No golden file and no source file is changed by this PR. CI runs the full suite.The order fix moved lines and changed none. Run from a checkout of this branch: it folds the parent commit
ac953e3bafresh, adds the upgrade notes' lines and the one new heading, and compares the sorted non-blank lines with the committedCHANGELOG.md:It prints
same lines: only moved. Every bullets-only block now sits directly under its own category (checked: 0 misplaced), and no heading lacks its blank lines.Review: the CodeRabbit CLI loop is dropped for v0.3.0 (developer, 2026-11-16, budget). Earlier CLI records on this PR cover heads up to
3876a0e6. Coverage for the final head is the in-PR CodeRabbit review, CI and the coordinator's verification.The one-off script that moved the blocks (not committed)
It ran after the fold and after the upgrade notes were inserted, with a copy of
changelog.d/taken before the fold asFRAGMENTS_SNAPSHOT_DIR.The remaining two commits (on the coordinator's go, after the developer's approval)
## [0.3.0] — YYYY-MM-DD, the UTC day the developer tags (expected 2026-11-17).TZ=UTC uv run python tests/test_hashing/golden/generate_golden_hashes.py --release 0.3.0. It appends the release revision to the golden history ofsrc/orcapod/contexts/data/v1.jsonand pins it insrc/orcapod/contexts/released_manifests.json(v1's first release: alsoreleased_inand the manifest pin). Before committing, its recorded date is checked against the heading. The Release workflow refuses a release without it. After it, a released golden value never changes; any change needs a new data context. If anything lands onmainafterwards, or the tag moves to another UTC day, the freeze is dropped and run again.No version bump, tag, Release workflow run, push to
nauticalabor setting change is part of this PR.🤖 Generated with Claude Code
Summary by CodeRabbit