Skip to content

chore(release): mark main as 0.7.0 development - #2344

Open
DecisionNerd wants to merge 1 commit into
mainfrom
chore/1095-main-0-7-0-dev
Open

DecisionNerd wants to merge 1 commit into
mainfrom
chore/1095-main-0-7-0-dev

Conversation

@DecisionNerd

@DecisionNerd DecisionNerd commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Step 10 of #1095: v0.6.0 is tagged at 7af4ecd, so this moves main to the next development version, 0.7.0-dev, as RELEASING.md ("Development version") requires. Issue #1095 stays open after this PR; it is not the close gate.

Changes

  • python3 scripts/set_release_version.py 0.7.0-dev: Cargo 0.7.0-dev, Python 0.7.0.dev0, npm 0.7.0-dev.0. The setter also refreshed the GDC runner source digests in the benchmarks/ acquisition and identity files. make release-version-check reports the versions as aligned.
  • Project-skill compatibility moves from >=0.6.0-dev <0.7.0 to >=0.7.0-dev <0.8.0, the same way chore(release): mark main as 0.6.0 development #1818 handled 0.6.0-dev. This covers the native validator (graphforge-api repository/skills.rs), the agent-skills compatibility.json, package.json and README, scripts/sync_project_skills.py, and the canonical project-skills/manifest.json. The packaged copies were regenerated with sync_project_skills.py --write. The validator test now also checks that the 0.6 range is rejected.
  • RELEASING.md now gives the 0.7.0 cycle as the example.

Regenerated from the 0.7.0-dev build (no hand edits)

I followed tests/fixtures/hub/README.md in order: generate_hub_fixture -- --rebuild-source, then --update, then the receipts, then the four corpora.

  • tests/fixtures/hub/openalex-source/{data/graphforge-project.json,manifest-sha256.txt,tagmanifest-sha256.txt}
  • tests/fixtures/hub/generated/v1/{fixture.json,manifest.json,refs.json,objects/*}
  • tests/fixtures/portable/facade-verification-receipts.json: produced by gf --json portable verify --mode full|inspect on a private copy of the bundle. Only these fields changed: package_digest, transport_digest, producing_core_version, payload_bytes (+4), package-control bytes (+4) and graph_data_ratio_ppm.
  • docs/reference/hub-publish/v1/item-admission-conformance.json, docs/reference/hub-publish/v1/item-source-conformance.json, docs/reference/discovery/v1/item-resolution-conformance.json, crates/graphforge-protocol-wasm/tests/opendata-openalex-commitment.json

The changed file set matches #2343's fixture set. The diffs contain only version strings and the digests and lengths that follow from them.

Verification

  • cargo nextest run -p graphforge-cli --test hub_fixture --test portable -p graphforge-hub-publish --test item_admission --test item_source -p graphforge-discovery --test item_resolution -p graphforge-protocol-wasm --test corpus --test hub_documents, without the update variables: 51 passed.
  • cargo nextest run -p graphforge-cli --test hub_fixture: 4 passed.
  • cargo nextest run -p graphforge-api --lib repository::skills: 8 passed.
  • pytest tests/unit/test_project_skill_assets.py tests/unit/test_set_release_version.py: 55 passed.
  • node --test packages/agent-skills/tests/cli.test.mjs: 4 passed.
  • make check: passed.

Refs #1095

🤖 Generated with Claude Code


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

Advance main to 0.7.0-dev after the v0.6.0 release (#1095 step 10):
set the version with scripts/set_release_version.py, move the project-skill
compatibility range to >=0.7.0-dev <0.8.0 in the native validator and the
agent-skills package, regenerate packaged project skills, and regenerate the
Hub fixture, its verification receipts and the conformance corpora from the
0.7.0-dev build.

Refs #1095

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

coderabbitai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Pre-merge checks: Inconclusive 2

Failed Failed checks: 2 inconclusive

Check name Status Explanation Resolution
Title check Pending This assessment has not completed. The check will be retried on the next pre-merge check run.
Description check Pending This assessment has not completed. The check will be retried on the next pre-merge check run.
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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 tooling Developer tooling and automation labels Nov 11, 2026
@greptile-apps

greptile-apps Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] This PR appears safe to merge.

Summary

Moves main to the 0.7.0 development cycle.

  • GraphForge packages now use the 0.7.0 development version across Rust, Python, and npm.
  • Project skills now declare and check compatibility with the 0.7 development cycle.
  • Generated Hub, portable, and benchmark records now match the 0.7.0 development build.

No actionable issues were found.

Reviews (1) · Last reviewed commit: "chore(release): mark main as 0.7.0 devel..." · Reviewed by Greptile

This branch has not been deployed

No deployments
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 tooling Developer tooling and automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant