Repository navigation
Conversation
This branch has not been 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
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.
Dated, evidence-only follow-up to merged #1205. No runtime, dependency, workflow or version changes; no upload or retry.
Verified October 14: eight of 22 frozen 0.2.0 files match PyPI hashes/sizes and are not yanked. Fresh Linux CPython 3.12.3 consumer installs all eight released packages with native 0.1.3. 38 unchanged contract tests, eight README quickstarts, pip check and the exact existing gist pass. pip-audit 2.10.1 reports no known vulnerabilities for 43 installed dependencies, with no skipped distributions.
Recovery run https://github.com/ruvnet/RuVector/actions/runs/38402061555 passed three-OS pre-upload checks and the native audit, but stopped on PyPI 429 after six additional wheel uploads. Three wheels and all eleven sdists remain missing. Post-publication three-OS checks were skipped and remain required. No fixed project-creation cooldown is claimed; the separate Trusted Publisher registration limit is not treated as applicable.
Files include reproducible commands, sanitized receipt/report hashes, coverage limitations, single-owner handoff, no-build decision and rollback. Existing tutorial: https://gist.github.com/ruvnet/2491c7631bf3e186e815196f52fd8954 . Draft for independent evidence review; do not auto-merge. Existing KGE/native/LionAGI lanes are untouched.