Skip to content

release: prepare 0.6.0 - #2343

Merged
DecisionNerd merged 1 commit into
mainfrom
release/1095-v0-6-0
Nov 11, 2026
Merged

DecisionNerd merged 1 commit into
mainfrom
release/1095-v0-6-0

Conversation

@DecisionNerd

@DecisionNerd DecisionNerd commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Refs #1095

Final release version change for GraphForge Core 0.6.0. Base: 1c7a99b17de22aaa68e9b9738ed7e807ed8c4610 (origin/main). This touches the same 52 files as the rc.8 preparation (#2312).

Commands and results

  • python3 scripts/set_release_version.py 0.6.0 → make release-version-check: set-release-version: aligned
  • cargo run -p graphforge-cli --example generate_hub_fixture -- --rebuild-source, then -- --update, then a check run with no flags: no drift
  • Receipts: same-build gf (graphforge 0.6.0), run on a private copy of opendata-openalex.gfpb: gf --json portable verify --mode full|inspect → full / structure_only
  • Corpora, in the documented order:
    • GRAPHFORGE_UPDATE_ITEM_ADMISSION_ARTIFACTS=1 cargo test -p graphforge-hub-publish --test item_admission native_admission_oracle_and_checked_in_wasm_corpus: 1 passed
    • GRAPHFORGE_UPDATE_DISCOVERY_ARTIFACTS=1 cargo test -p graphforge-hub-publish --test item_source generated_transitions_preserve_sources_and_cas_preconditions: 1 passed
    • GRAPHFORGE_UPDATE_DISCOVERY_ARTIFACTS=1 cargo test -p graphforge-discovery --test item_resolution generated_contract_and_native_resolution_agree: 1 passed
    • GRAPHFORGE_UPDATE_PROTOCOL_WASM_EXPECTED=1 cargo test -p graphforge-protocol-wasm --test corpus --test hub_documents: 5 + 1 passed, and the protocol-wasm expected files did not change
  • Reruns without update variables:
    • make test-rust ARGS="-p graphforge-cli --test hub_fixture": 4/4
    • make test-rust ARGS="-p graphforge-hub-publish --test item_admission --test item_source --test contract_artifacts": 15/15
    • make test-rust ARGS="-p graphforge-discovery --test item_resolution": 11/11
    • make test-rust ARGS="-p graphforge-protocol-wasm --test corpus --test hub_documents --test hub_control": 7/7
  • make check: passed

Diff review

A token-level diff of every regenerated file shows only these changes:

  • the version (0.6.0-rc.8 → 0.6.0)
  • the sha256 digests that cover the version
  • byte counts that shrink by exactly 5, the length difference of the version string:
    • summary length 2118 → 2113
    • payload_bytes 30581 → 30576
    • package-control 9706 → 9701
  • graph_data_ratio_ppm, which follows from the payload size

The .gfpb sizes did not change (tar padding).

Not changed (intentionally)

  • docs/contracts/hub-control/v1/conformance.json keeps producing_core_version: "0.6.0-rc.8". This is literal sample data in an input corpus with no generator, and no test ties it to the build version.
  • docs/guide/use-a-notebook.md pins the qualified 0.6.0rc8 wheel by SHA-256 and Publish run. Relabeling it would be false. It needs a follow-up once the 0.6.0 wheel is published.
  • The scripts/ci/test-package-native-cli.py test literal is not tied to the version.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Set every package to 0.6.0 and regenerate the version-dependent Hub
fixture, verification receipts and conformance corpora from this build.

Refs #1095

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions github-actions Bot added parser Changes to Cypher parser planner Changes to query planner executor Changes to query executor core Core source code changes testing Test coverage and testing infrastructure documentation Improvements or additions to documentation labels Nov 10, 2026
@greptile-apps

greptile-apps Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] This release preparation appears safe to merge; no actionable issues were found.

Summary

Promotes GraphForge from 0.6.0-rc.8 to 0.6.0 across Rust, Python, and npm packages.

  • GraphForge packages and fixtures now identify release 0.6.0.

Reviews (1) · Last reviewed commit: "release: prepare 0.6.0" · Reviewed by Greptile

@DecisionNerd
DecisionNerd added this pull request to the merge queue Nov 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 10, 2026
@DecisionNerd
DecisionNerd added this pull request to the merge queue Nov 11, 2026
Merged via the queue into main with commit 7af4ecd Nov 11, 2026
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Core source code changes documentation Improvements or additions to documentation executor Changes to query executor parser Changes to Cypher parser planner Changes to query planner testing Test coverage and testing infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant