[codex/interactive] fix(release): publish crate dependency chain - #75
Merged
Conversation
div0-space
force-pushed
the
fix/crates-index-poll
branch
from
August 24, 2026 04:04
ad44ea2 to
e6aa65e
Compare
Publish report-leptos, loctree-ast, loctree, and loctree-mcp in dependency order. Poll exact crates.io versions from a neutral directory and load release control from the workflow SHA while keeping source pinned to the immutable tag. Authored-By: codex <agents@vetcoders.io>
div0-space
force-pushed
the
fix/crates-index-poll
branch
from
August 24, 2026 04:05
e6aa65e to
0d35259
Compare
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.
Current state
Publish attempt 3 uploaded only
report-leptos 0.14.4.loctreenever reached upload: Cargo could not resolve its unpublishedloctree-ast = "^0.14.4"dependency. The old fallback then produced a false positive because fuzzycargo search loctree | grep 0.14.4matched another search row, so the workflow continued andloctree-mcpfailed on the still-absentloctree 0.14.4.There was a second recovery defect: the job checks out the immutable release tag, so a poller added after that tag would not exist in the release worktree.
Change
report-leptos -> loctree-ast -> loctree -> loctree-mcploctree-astpublishable in the local release driver and include it in its publish ordercargo info --registry crates-io crate@version, never from the matching local workspacerelease-srcand the poller from the exactgithub.workflow_shaunderrelease-controlVerification
bash tests/crates_io_index_wait_contract.sh: PASSbash tests/preflight_contract.sh: PASSRecovery
After merge, start a fresh
Publish Releasesdispatch from mergedmainwith tagv0.14.4. Do not rerun the old failed attempt: reruns retain the old workflow definition. The fresh run will use release-control from the merged workflow commit while publishing the immutable tagged source, skipreport-leptosexactly, publishloctree-ast, then unlockloctreeandloctree-mcpplus all downstream platform/thin/npm/monorepo jobs.