Record ctrlrun-langchain 1.0.0, after the upload succeeded - #227
Conversation
PyPI serves 1.0.0 declaring ctrlrun>=0.12,<0.13, verified by installing it from the index into a clean venv rather than by reading the workflow's tick. The table row and the RECORDED entry both come from PyPI's own requires_dist, which is the whole point of the comparison: a record taken from the tree would agree with the tree by construction, which is how this guard died at 0.11.0. langchain leaves `unreleased` in the same edit, because it is now released. The RECORDED guard was mutation-checked: claiming a range PyPI does not serve fails it. Signed-off-by: Arpan Ghoshal <contact@arpanghoshal.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 5 remain after this review. 📝 WalkthroughWalkthroughThe adapter registry now publishes LangChain version 1.0.0 for kernel versions ChangesLangChain adapter publication
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The LangChain publication metadata is internally consistent, with no unresolved merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
ctrlrun-langchain1.0.0 is on PyPI. This is the record of that, written after the fact ratherthan beside the change that motivated it, which is the rule the file states and the rule that
was not followed at 0.11.0.
Verified from the index, not the tick
PyPI's own
requires_distfor 1.0.0 isctrlrun<0.13,>=0.12, and both thePUBLISHED.tomlrow and the
RECORDEDentry are taken from there. A record read off the tree would agree withthe tree by construction, which is exactly how this guard died one release after it was written.
langchainleavesunreleasedin the same edit, because it is now released.The release itself
The first publish run failed with
Non-user identities cannot create new projects— PyPI'swording for "no pending publisher under this name". The publisher was added after the tag fired;
re-running the failed job succeeded with no changes to anything.
Evidence
Summary by CodeRabbit
New Features
Documentation