Repository navigation
chore(release): mark main as 0.7.0 development - #2344
Open
DecisionNerd wants to merge 1 commit into
Open
DecisionNerd wants to merge 1 commit into
DecisionNerd wants to merge 1 commit into
Conversation
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>
Pre-merge checks:
|
[Medium impact] This PR appears safe to merge.
|
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.
Step 10 of #1095: v0.6.0 is tagged at 7af4ecd, so this moves
mainto the next development version,0.7.0-dev, asRELEASING.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: Cargo0.7.0-dev, Python0.7.0.dev0, npm0.7.0-dev.0. The setter also refreshed the GDC runner source digests in thebenchmarks/acquisition and identity files.make release-version-checkreports the versions as aligned.>=0.6.0-dev <0.7.0to>=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-apirepository/skills.rs), the agent-skillscompatibility.json,package.jsonand README,scripts/sync_project_skills.py, and the canonicalproject-skills/manifest.json. The packaged copies were regenerated withsync_project_skills.py --write. The validator test now also checks that the 0.6 range is rejected.RELEASING.mdnow 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.mdin 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 bygf --json portable verify --mode full|inspecton a private copy of the bundle. Only these fields changed:package_digest,transport_digest,producing_core_version,payload_bytes(+4),package-controlbytes (+4) andgraph_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.jsonThe 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
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.