release: publish crates under graphforge namespace - #270
Merged
Merged
Conversation
|
Important Review skippedToo many files! This PR contains 557 files, which is 407 over the limit of 150. To get a review, narrow the scope: Upgrade to Pro+ to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (131)
📒 Files selected for processing (557)
You can disable this status message by setting the Comment |
github-actions
Bot
added
parser
This comment has been minimized.
This comment has been minimized.
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
1 participant
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
gf-*/gf_*tographforge-*/graphforge_*graphforge-cli, while keeping the Python and Node implementation crates Cargo-privateDecisionNerdownershipPublish to PyPI, npm, and crates.io, using the ESC-projectedCARGO_REGISTRY_TOKENValidation
cargo check --workspace --lockedcargo clippy --workspace -- -D warningscargo test --workspace --locked --no-fail-fastcensus: all targets passed except the two expected M20/M21 owner-inventory digests; reviewed those owner-only changes, regenerated their checksums, then both exact contract tests passedmake pre-push-fastpython3 scripts/ci/crate-publish-plan.py check(15 crates)Closes #269
Refs #196
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Note
Rename all crates from
gf-*tographforge-*namespace for crates.io publicationgf-*namespace tographforge-*(e.g.gf-api→graphforge-api,gf-storage→graphforge-storage) and updates all internal import paths accordingly.gf-bindings-py→graphforge-bindings-py,gf-bindings-node→graphforge-bindings-node) and updates all CI scripts, workflow files, tooling paths, and documentation references.scripts/publish_crates.pyto automate crates.io publication: packages each crate viacargo package, checks existing crates.io versions, publishes withcargo publish --locked, polls for indexing, verifies checksums, and confirms owner before completing.ownerstrings fromgf-*tographforge-*(e.g. ingraphforge-provenance,graphforge-knowledge,graphforge-storage), which changes the JSON produced by schema inventory endpoints.scripts/publish_crates.pywith a registry token instead of only recording a dry-run plan.ownerfields or contract JSON will seegraphforge-*strings instead ofgf-*.Macroscope summarized c75e3cb.