Conversation
…s publish concerns only) Second preflight on main (run 35947805768) failed on two more kit gates that duplicate consumer CI: fmt/clippy/workspace tests run without the consumer's tool bootstrap (sc-compose missing for the passthrough tests), and package checks that tried to registry-verify publish = false crates. sc-publish #118/#120 (main cbb9ce08) remove those gates per #67. Kit files re-rendered by the kit installer; dry-run in sync. Release tooling only. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
release(1.6.1): advance sc-publish kit to cbb9ce08 (preflight verifies publish concerns only)
…st, in publish order The kit's list-publish-plan emits every [[crates]] entry in manifest file order. Release run 35952487967 failed on the first entry, atm-graft-python, whose Cargo.toml has publish = false. Remove the two PyPI-only bridge crates from [[crates]] (they stay under [[python_packages]]/[[python_distributions]]) and order the remaining blocks by publish_order. The resulting plan is identical to the 1.6.0 upload sequence. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
release(1.6.1): manifest declares only crates.io-published crates, in publish order
…eel once Release run 35958433737 published every crate and then failed in the release job's Python asset verification: a setuptools sdist carries a second PKG-INFO under *.egg-info, and a pure-python build yields one universal wheel that three OS legs collapse into. atm-core's 1.6.0 copy of release_artifacts.py carried both fixes (sc-publish#74, #75); the phase-bc kit re-render dropped them. Match only the root-level sdist PKG-INFO again, and build hermes-atm on a single wheel leg so the expected and collected wheel counts agree. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Publish PyPI run 36017176129 checked out the immutable tag v1.6.1 and ran that commit's release_artifacts.py, reproducing the sdist rejection that #1592 fixed on main. The workflow never builds from source; the checkout only supplies the verify tooling and the manifest, so it must come from the dispatched commit (sc-publish#76, the v1.4.4 fix the phase-bc re-render dropped). Release assets are still downloaded by tag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
release(1.6.1): check out the dispatch ref in the PyPI publish workflow
This branch was successfully deployed
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
2 participants
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.
Summary
Back-propagates the 1.6.1 release fixes from
maintodevelop.developis an ancestor ofmain, so this is a fast-forward with no conflicts.Commits carried over:
Release state
atm-core 1.6.1 is published on crates.io (15 crates), GitHub Release v1.6.1, PyPI (atm-graft, atm-query, hermes-atm), Homebrew, Scoop and Winget. Publisher task
release-1-6-1-root-release-6closed complete.🤖 Generated with Claude Code