Repository navigation
Install microcosm-emitter 0.2.1 from PyPI - #1279
Merged
Merged
Conversation
Replace the draft-only Git source pin on emitter commit 12624a1, which predates the bounded service startup and final concurrency fixes, with the exact PyPI release 0.2.1 that the emitter's release workflow published. uv.lock now records the registry wheel and source archive with hashes, and the approved primary-QRF worker-identity lock digest follows the regenerated lockfile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
anth-volk
force-pushed
the
build/emitter-from-pypi
branch
from
October 14, 2026 17:49
17e508c to
4a4de39
Compare
anth-volk
marked this pull request as ready for review
October 14, 2026 19:43
juaristi22
added a commit
that referenced
this pull request
Oct 14, 2026
The rebase onto main 121fd4d (#1256, #1279) settled the generated files with main's side. Regenerated on the rebased tree: the gate battery digests (main's export allow-list line beside this branch's), the coverage manifest's source digests and the H2 fixture, whose synthetic CGT asset-type facts follow the locked engine. The rendered stages are unchanged. uv.lock merged cleanly (microcosm-emitter 0.2.1 from PyPI beside policyengine-uk 2.130.1), and the lock commits pin its new digest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 14, 2026
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.
This PR replaces the draft-only Git source pin on
microcosm-emitterwith the exact PyPI release 0.2.1. It was the last item indocs/orrery-publication.md's "Deferred migration prerequisites", and it was Microcosm's only Git-pinned dependency.The previous pin, commit
12624a1, had diverged from the emitter'smain. It lacks PolicyEngine/microcosm-emitter#11 (bounded service startup) and the final concurrency fixes from #9. 0.2.1 contains both. The emitter's release workflow published it with trusted publishing: every merge to the emitter'smainnow publishes a new version automatically.Changes
packages/microcosm-build/pyproject.toml:microcosm-emitter==0.2.1, and the[tool.uv.sources]Git override is removed.uv.lock: regenerated. Only themicrocosm-emitterentries change: the registry source, plus the wheel and source archive with hashes. The emitter's dependencies are unchanged, and no other package moved.APPROVED_UV_LOCK_SHA256inmicrocosm.build.us_runtime.worker_identitynow holds the new lockfile digest (6b32bcb1…).docs/orrery-publication.md: "Deferred migration prerequisites" is replaced by "Emitter dependency" (how to adopt a new release) and "Migrating an existing workstation" (the unchanged queue-upgrade guidance).Compatibility
start_services,GraphPublicationClient,default_spool_path,publish_graph,publication_inventory, the publication contracts,LocalTelemetryEmitter,TelemetryRun,DEFAULT_HEARTBEAT_SECONDSandSERVICE_START_WARNING.12624a1and 0.2.1, none of those names or their parameters changed. The only addition is aphasefield on the startup-failure diagnostic.STARTUP_TIMEOUTfrom microcosm-emitter#11.Validation (local, macOS, Python 3.14)
uv sync --all-packages --lockedinstallsmicrocosm-emitter0.2.1, anduv run ruff check .passes.test_uk_orrery_publication.pyalone also passed (15).mainat1cfbf7d8,uv lock --checkand Ruff passed, the lockfile digest still matchedAPPROVED_UV_LOCK_SHA256, andtest_emitter_adapter.pywithtest_uk_orrery_publication.pypassed (34).test_spawned_workers_score_identically_to_sequential_clican't run on the local interpreter.tools/score_us_release_head_to_head.pyrefuses--worker-max-sliceson Python 3.14.6 ("replacing a recycled worker can deadlock the pool"). That guard checks only the interpreter version, so it is unrelated to this change. CI runs it.No new runtime variable, credential or service is introduced.
🤖 Generated with Claude Code