Skip to content

memory: v4.42.3 shipped and rolled out to the four family repos #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
acn-ericlaw merged 1 commit into from
Oct 5, 2026
Merged

memory: v4.42.3 shipped and rolled out to the four family repos #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions memory/sessions/2026-10-05-171742.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Session (2026-10-05T17:17:42.089Z)

**Agent:** Claude Code

## What happened

**v4.42.3 shipped (since the previous log).** PR #20 merged as `e50e5e3`; tagged `v4.42.3` (lightweight, on the
merge commit) and published the release, marked Latest. Every run on the merge commit green (`docs`, `tests`,
`agent-memory`, and the pair the tag push started). The continuity status line already read v4.42.3 — the release
commit carried it this time.

**Rolled out to the four family repos (maintainer: "upgrade the four family repos to v4.42.3"),** by the
`family-upgrade-worktree-path` procedure. PRs, all merged: mercury-composable #507 (squash `0e83c050`), mercury
#355 (`12a30d6b`), mercury-python #41 (`27627c48`), mercury-nodejs #109 (`373975d5`). Per repo: reconcile re-copied
`REVIEW.md` and `.agent/schema.md` — all eight copies stock 4.42.2 before (warn-before-clobber: staleness only); no
semantic step (protocol unchanged); stamped 4.42.3; lightweight log `(none)` with its post-log lint count
(mercury-composable 21 warnings, mercury 4, mercury-python 4, mercury-nodejs 3 — 0 errors everywhere); converged;
`--staged` ok. Post-merge `agent-memory` floor green on all four; mercury-python and mercury-nodejs CI green;
mercury-composable and mercury builds still running at record time (the change touches no code). GitHub deleted
the four remote branches; the local ones were removed after an ancestry check (mercury-composable: tree equality
with its squash commit).

**mercury-composable's pending review.** Its two overdue conventions now read 23 sessions since last use; the
team's evidence thread (`step6-release-sweep-gaps`) is untouched. The Snyk fact still names its two paths in plain
text; PR #507 spells out what the v4.42.3 check does once they are backticked — keeps both paths (busy over all
history, not in the window), finds `9e515825`, maps it in history order to the release session's log. The decision
test and the declaration stay with their review. No other family repo has an overdue live fact.

## Memory References

- Referenced: `family-upgrade-worktree-path` (the procedure followed), `upgrades-additive` (the warn-before-clobber
check gated every re-copy), `target-repo-scope-only` (each upgrade confined to its target worktree; the
mercury-composable fact and thread read, not edited), `declare-consulted-references` (the v4.42.3 rule rolled
out; it decided what #507 tells the pending review), `github-origin-mercury-go` (release and PRs to the org
homes)
Loading