Repository navigation
Closed
Description
Filed by the coordinator of epic #154, with the operator's approval (2026-11-15). This runs next. #185 is waiting on CannObserv/watcher#420.
Why
- cannobserv tagged v0.47.0, v0.48.0 and v0.48.1 at 2026-11-14T20:16Z, 2026-11-14T23:25Z and 2026-11-15T04:07Z. All three versions are on the co-pypi index for
co-core,co-core-aioandco-core-sync. That was read unbounded asco-pypi-reader@at 04:2xZ and again at 05:4xZ [measured]. - The repo rule is to pin the current minor (AGENTS.md, Environment & Tooling). The pins at
pyproject.toml:447-449read>=0.46.0,<0.47, so the lock can't take 0.48. - Two minors at once.
co-core-aioandco-core-sync0.48.x requireco-core>=0.48,<0.49, so the three packages move together. 0.47 adds nothing we'd stop at.
What 0.47 and 0.48 change [stated by CHANGELOG.md at v0.48.1]
- 0.47.0 is a breaking minor, in the WordPress and transcript models.
cannobserv.ext.wordpress.blocks.get_wp_automation_disclosure_blockandprepare_block_attributeare removed (#672).TranscriptSpeakerModel.relationship_idis renamedrole_assignment_id. The old name still validates (#469 part C).- It adds the Automation Disclosure block builder, the transcript serializer, and
co_core_sync.services.disclosure_catalog(#676).
- 0.48.0 is a breaking minor:
DisclosureServiceModel.service_typenow takes a catalog value only. A label raisesValueError(#678). - 0.48.1 is a patch.
- It adds
disclosure_catalog.add_service_type(#680). - Drive's
files.get,files.listandfiles.deletenow retry transient failures (num_retries=3). Writes are still sent once (#601). - A retried delete whose first attempt landed can now raise
GdriveApiError(404).
- It adds
The closure diff, already run [measured 2026-11-15T05:4xZ by the coordinator]
The wheels were fetched with bash scripts/co-pypi.sh uv run --no-project python scripts/co_pypi_wheels.py --dest <dir> --version 0.46.1 --version 0.48.1 co-core co-core-aio co-core-sync. Then scripts/co_core_closure_diff.py 0.46.1 0.48.1 --wheels <dir> printed:
58 files at 0.46.1, 58 at 0.48.1. 4 not identical:
- `version-only` co_core/__init__.py
- `version-only` co_core_aio/__init__.py
- `version-only` co_core_sync/__init__.py
- `changed` co_core_sync/drivers/gdrive.py
Requires-Dist:
- co_core: unchanged
- co_core_aio: removed `co-core<0.47,>=0.46`; added `co-core<0.49,>=0.48`
- co_core_sync: removed `co-core<0.47,>=0.46`; added `co-core<0.49,>=0.48`
Third-party imports (at 0.48.1): google, google_auth_oauthlib, googleapiclient, httpx, pydantic, redis, requests, urllib3 (unchanged).
Dynamic imports: the same two co-core-sync `drivers/` sites.
changed means read it.
drivers/gdrive.pyis in the closure throughco_core_sync.drivers.- Replicator has no Drive writer.
gdriveis refused asprovider_disabled(src/worker/aliases.py:49,src/worker/replicate.py:401), and/etc/replicator/replication-aliases.jsonholds nogdrive-alias [measured]. --diffshows the retry and nothing else [measured by the coordinator]:DRIVE_NUM_RETRIES = 3, and.execute(num_retries=DRIVE_NUM_RETRIES)onfiles().delete,.getand.list. Re-read it from your own wheels and say so in the pin comment.
No code change is expected. Re-run the diff from the wheels you lock, and paste it in.
Steps
- List the index unbounded first (a lock probe at
<1). If something newer than 0.48.1 has appeared, widen to it and say so here. - Move all three pins to
>=0.48.0,<0.49. The lock will take 0.48.1.- Nothing here depends on 0.48.1's changes, so the patch floor stays at
.0, per the rule in DEPENDENCIES.md. If you floor at 0.48.1 instead, say why here. - Run
uv lock --upgrade-packagefor the three packages throughbash scripts/co-pypi.sh uv …, in an isolated venv (the Converge storage on the cluster content-addressed model #114 rule; the worktree steps are in thedevelop-in-worktreesnotes and DEPENDENCIES.md). - Expect the lock diff to be the three
co-core*entries plus therequires-distmirror.
- Nothing here depends on 0.48.1's changes, so the patch floor stays at
- Update every literal of the current minor.
git grep -nE '0\.46|<0\.47' -- ':!uv.lock' ':!docs/plans'onf2a4333lists them [measured]:AGENTS.md:29;docs/DEPENDENCIES.md:96, and:100, which names "at 0.46.1" for the lazy__getattr__sites;.socraticodecontextartifacts.json:166, which owes acodebase_updatein the same change (AGENTS.md, Code Exploration Notes);pyproject.toml:10-55, the pin comment: replace the 0.45 → 0.46.1 report with the 0.46.1 → 0.48.1 one;tests/test_dependency_index.py:63. Its bound moves to>=0.49and its docstring gets today's reading. It goes red on the lock move, which is expected: Catch up co-core 0.41 → 0.44 (three minors on the co-pypi index; widened from 0.42 at review) #184, Catch up co-core 0.44 → 0.45 (co-pypi index; closure diff version-only) #192 and Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199 moved the same line.
- Gates. Save the full output of each to files.
- The default suite. The baseline on
f2a4333is 2062 passed, 1 skipped, both clean and loaded. -m integrationon a scratch broker.-m browserin the delegated scope.-m gcs.tests/ciandtests/deploy(181 together withtests/test_deploy.pyandtests/test_load_env.pyon the host).- ruff.
- CI green by job.
- The real-wheel closure test, with
REPLICATOR_TEST_CLOSURE_WHEELSfilled at 0.36.0 and 0.37.0 by the fetcher.
- The default suite. The baseline on
Since #202: a session started before 2026-11-15T05:33Z lacks the replicator group. Run id -nG first, and use sg replicator -c '…' if replicator is missing (DEPLOYMENT.md, The service user).
Done when
- The lock holds 0.48.1 ×3 from the index, with hashes, and
uv lock --checkis clean. scripts/deploy.sh(via shipping-work) has put the merge SHA live, and on that build:worker readyshowscapture,browser_fetchandpersistasenabled;- the release venv (
/srv/replicator/live/.venv) has 0.48.1 ×3; - the fetch-policy replay is clean;
- the worker runs as
replicatorwithNRestarts=0.
- The pin comment carries the closure-diff report.
The deploy restarts the worker.
Metadata
Metadata
Assignees
Labels
No labels
Activity
gregoryfoster commentedon Nov 15, 2026
Pre-flight: widen to 0.48.2 (coordinator, 2026-11-15T16:4xZ)
Correction to the body's target. cannobserv tagged v0.48.2 at 2026-11-15T06:51:22Z, about 75 minutes after I filed this. It's on the co-pypi index for all three packages [measured 16:4xZ, unbounded]. So step 1's "widen" applies now: the lock takes 0.48.2. The pins stay
>=0.48.0,<0.49.What 0.48.2 changes [stated by its CHANGELOG]. It's a patch, with no signature changes and no removals:
find_by_ulidis added onperson,organization,roleandassignment(#699).GdriveDeleteIfPresentandGdriveDriver.delete_if_presentare added.upload_one's REPLACE now uses them (#692).The closure diff, re-run [measured, using wheels fetched by
co_pypi_wheels.py]:Read with
--diff, the twochangedfiles hold only Drive changes:effects/gdrive.pyadds theGdriveDeleteIfPresentdataclass and theGdriveDeleteOutcomeenum, and adds the new effect to theGdriveEffectunion.drivers/gdrive.pyadds 0.48.1'snum_retriesand 0.48.2'sdelete_if_present.Replicator has no Drive writer (the body's
provider_disabledreasoning), so no code change is expected still. Paste the 0.46.1 → 0.48.2 report into the pin comment.Literal sites: unchanged from the body.
tests/test_dependency_index.pyrecords "nothing past 0.48.2".[-]Catch up co-core 0.46 → 0.48 (0.48.1)[/-][+]Catch up co-core 0.46 → 0.48 (0.48.2)[/+]gregoryfoster commentedon Nov 15, 2026
Pickup review (implementer, 2026-11-15T20:1xZ)
Body + pre-flight checked against
origin/main=f2a4333.Holds as briefed
>=0.46.0,<1(19:59:58Z) resolvesco-core,co-core-aio,co-core-sync0.48.2. Nothing past it. The pre-flight's widening stands; pins>=0.48.0,<0.49, floor.0.git grep -nE '0\.46|<0\.47' -- ':!uv.lock' ':!docs/plans'onf2a4333gives exactly the body's list.co_pypi_wheels.py --version 0.46.1 --version 0.48.2): identical to the pre-flight's — 58/58 files, 5 not identical, 2changed, both Drive. Same result withtests/added as a root. Read with--diff:effects/gdrive.pyaddsGdriveDeleteIfPresent,GdriveDeleteOutcomeand the union member;drivers/gdrive.pyaddsDRIVE_NUM_RETRIES = 3onfiles().delete/.get/.listanddelete_if_present. Nothing else.KNOWN_PROVIDERS = ("gcs",)(src/worker/aliases.py:62, reasoning at:45-52);/etc/replicator/replication-aliases.jsonhas 0gdrive-matches [measured]. Nogdrive/Gdriveuse insrc/orscripts/beyond the alias pattern and docstrings.Corrections to the body's "What 0.47 and 0.48 change" — from a whole-wheel
diff -rq(dist-info excluded), not the CHANGELOG:cannobserv.ext.wordpress.blocks.get_wp_automation_disclosure_blockandprepare_block_attributeappear in no.pyof the 0.46.1 wheels; at 0.48.2 they appear only in docstrings of two new modules (pure/adapters/wordpress/blocks.py,disclosure.py). Same shape as Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199'swp_view_*_url.service_typebreak has no 0.46.1 surface here.pure/models/disclosure_service.pyis new on this move. And at 0.48.2 the label refusal is raised by the WordPress adapter (disclosure.py:_service_type_value) when a block is built, not at model construction — the model only refuses blank.pure/models/transcript_speaker.py). Outside the closure, also changed or added: co/v1exceptions.py,urls.py,disclosure_catalog.py;pure/models/transcript*.py,disclosure_*;workflows/upload.py; co-core-syncrunner.pyandservices/(_co_v1,amendment_settings,assignment,organization,person,role,sponsorship_settings, newdisclosure_catalog). Nothing insrc/,scripts/ortests/reaches any of them.Conclusion unchanged: no code change expected. Proceeding: worktree + isolated venv; I'll confirm the fetched wheels' sha256 against the new lock's hashes before pasting the report.
gregoryfoster commentedon Nov 15, 2026
Build report (implementer, 2026-11-15T20:2xZ) — PR #207, branch head
cae0dce9364dLock: 0.48.2 ×3 from co-pypi, with hashes; diff = the three
co-core*entries +requires-distmirror;uv lock --checkclean. The six diffed wheels (0.46.1, 0.48.2) match the old and new lock's sha256 — the report in the pin comment is from the locked wheels. Floor stays.0.Gates (worktree, isolated venv; full output saved per gate):
f2a4333(re-measured here)-m integration(scratchredis-server7.0.15, loopback)-m browser(user scope,Delegate=yes)-m gcs(test buckets)tests/citests/deploytest_deploy.pytest_load_env.pyREPLICATOR_TEST_CLOSURE_WHEELSat 0.36.0/0.37.0)test_reproduces_136_for_0_36_to_0_37passed, not skippedtest_dependency_index.py::test_the_locked_versions_sit_inside_the_pinwent red on the lock move as expected, green after the>=0.49bound.Open before close: merge, CI on the merge SHA,
scripts/deploy.sh(restarts the worker), the Done-when checks on the live build, andcodebase_updatefrom the main checkout for the manifest edit. Paused for the operator before shipping.#206 docs: CR 1 — the two changed Drive modules cannot load here, mea…
gregoryfoster commentedon Nov 15, 2026
CR round 1 (blanket
--fix), PR #207 head096afd362d60:googleapiclientisn't installed (no[gdrive]extra, absent fromuv.lock),drivers/gdrive.pyimports it at module top, and importingsrc.worker.main+src.storage.local_storeloads neither module [measured].codebase_updateruns from the main checkout after the merge (SocratiCode indexes by absolute path).Post-fix gate:
uv lock --checkclean, ruff clean, default 2062 passed / 1 skipped; CI lint/test/gcs/browser ✅ on096afd362d60. Still paused before shipping.Merge #206: co-core 0.46 → 0.48, two-minor catch-up
gregoryfoster commentedon Nov 15, 2026
Shipped —
59fb240live (PR #207, merged 2026-11-15T23:42Z)>=0.48.0,<0.49×3; lock 0.48.2 ×3 from co-pypi with hashes;uv lock --checkclean. Floor stays.0.--diffreading, and CR 1's measured fact: neither changed Drive module can load here.AGENTS.md,docs/DEPENDENCIES.md, the manifest,tests/test_dependency_index.py(>=0.49).59e1b8d(pin + lock + test),cae0dce(docs),096afd3(CR 1), merge59fb240.Done when, on the live build [measured 23:44–23:46Z]:
scripts/deploy.sh 59fb24082f7e…exited 0;/srv/replicator/live→releases/59fb24082f7e; CI run 43776215180 green on lint, test, gcs, browser.worker ready(build59fb24082f7e, 23:44:16Z):persist,capture,browser_fetchallenabled./srv/replicator/live/.venv: co-core, co-core-aio, co-core-sync 0.48.2.replicator,NRestarts=0, noreplicator-failurerecords.Known limits:
dependency-contractartifact re-embedded at 23:43Z (34/34 artifacts indexed), but the code index's incrementalupdatewas refused — another process held this project's index lock (capped driver and MCP both). The changed files arepyproject.toml,uv.lock, one test and docs; the lock holder's watcher or the nextupdatecatches them up.-m integration,-m browserand-m gcsran oncae0dce; CR 1 (096afd3) changed only apyproject.tomlcomment, and CI re-ran browser and gcs on it.For #154:
wp_view_*_url, here 0.47.0's disclosure-block removals): a brief's "what changes" should be read as a whole-wheel diff, not the CHANGELOG.gregoryfoster commentedon Nov 16, 2026
Verified (coordinator, epic #154, 2026-11-15T23:5xZ)
I read all of this in this check-in [measured]:
f2a4333..59fb240. Three commits (59e1b8d,cae0dce,096afd3) and the merge59fb240(PR #206: co-core 0.46 → 0.48, two-minor catch-up #207, merged 23:42:01Z).mainis clean, atorigin/main.update-uv-graphpassed on59fb240; lint, test, gcs and browser passed on096afd3./srv/replicator/livepoints toreleases/59fb24082f7e, and the previous release isf2a43335c6b0./run/replicator/build-id.envreadsBUILD_ID=59fb24082f7e.replicator:replicator. Its cwd is the release, it has 0 maps under/home, andNRestarts=0.NoNewPrivileges,ProtectSystem=strict,ProtectHomeandPrivateTmpare all still on.check_redis_floorlines.worker readyshowspersist,captureandbrowser_fetchasenabled. The policy replay read 503 messages and applied 10 hosts.journalctl -t replicator-failureis empty, and no unit has failed. Root disk is at 55%.59fb240, run by me:test_deploy.py:1049(not run from an exe.dev session), because I launched the run detached from my session. Run in the foreground, the same test passes. So the result matches your 2062 passed, 1 skipped.ruff check,ruff format --checkanduv lock --checkare all clean.codebase_searchreturnstest_dependency_index.pywith "nothing past 0.48.2" and the>=0.49bound, andcodebase_context_searchreturns DEPENDENCIES.md at>=0.48.0,<0.49.Carried to the epic:
-m integration,-m browserand-m gcswere run locally oncae0dce, before CR 1. CR 1 changed only a comment, and CI re-ran browser and gcs on it.Nothing is owed.