Repository navigation
release(version): start 0.15.1 development - #1320
Conversation
ragnorc
left a comment
There was a problem hiding this comment.
Review of #1320 at 5458f181
Outcome: ready to merge. No blocking items. Three optional items.
Why, what, how, impact
- Why. v0.15.0 is tagged. Main still says
0.15.0. An edge build of main reports0.15.0-edge+<commit>, and that version sorts before0.15.0. So the edge publisher refuses every build until the version moves. - What. All 22 workspace packages move from
0.15.0to0.15.1, with their path-dependency pins.Cargo.lock,openapi.json(info.version) and the skill'smetadata.versionmove with them. - How. A mechanical edit. The PR has one commit on the current main tip (
afc4be77). - Impact. Edge builds can publish again from the next main commit.
omnigraph version, the skill export and the served OpenAPI document report0.15.1. The HTTP contract (0.14) and the storage formats do not change. Runtime behavior does not change.
Blocking
None.
Optional
-
The description names a change that this diff does not make. It says
changelog.d/release.jsonnow namesv0.15.1with baserefs/tags/v0.15.0. That file is not in this PR. It already landed on main with #1291 (cf2dce58). The file is correct; only the text is stale. Please edit the description before you merge, so that the squash commit does not claim a change that it does not make. -
docs/user/install.md:204now gives an example version that cannot occur. It says an edge build reports a version "such as0.15.0-edge+9c2b367". The next sentence says that edge builds publish only while the package version is above the latest stable release. With v0.15.0 published, the guard refuses0.15.0-edge.0.15.1-edge+9c2b367agrees with the rule. #1273 made the same edit for 0.15.0.AGENTS.md:32("Version surveyed: 0.15.0") is similar: #1273 changed that line, and the 0.14.1 opening (#1140) did not. If the line means "the version this snapshot describes", change it here too. If not, leave it. -
The version is written in about 84 places, so each bump edits 108 lines in 25 files. There are 22
[package]versions and about 62 intra-workspaceversion = "…"pins. Checks already guard the derived copies: the committed-spec test inomnigraph-server/tests/integration/openapi.rsguardsopenapi.json,check-docs.pyguards the skill version, andcargo metadata --lockedguardsCargo.lock. Nothing keeps the 22 package versions and the pins in agreement. A missed pin passes silently on a patch bump, because"0.15.0"means^0.15.0, which0.15.1satisfies. The miss shows only at the next minor bump, as a resolution failure.- A smaller design uses Cargo workspace inheritance. Put
[workspace.package] version = "0.15.1"in the root manifest andversion.workspace = truein each member. Declare each internal crate once under[workspace.dependencies]with itspathandversion. Members then writeomnigraph-core = { workspace = true }, and addfeatures = [...]where they need them. A bump then edits one line, plus the derived copies above.cargo publishresolves inherited fields (Cargo 1.64 and later). - Cost: a one-time edit of 22 manifests. Two readers parse the literal
[package] versionofcrates/omnigraph-cli/Cargo.tomland must change: the regex incheck-docs.py, and thetomllibstep inrelease-edge.yml("Refuse a version that sorts before the latest stable release"). Both can read the root[workspace.package]table orcargo metadata. - After five more bumps: about 5 manifest lines instead of about 540. This is a separate PR, not a condition for this one.
- A smaller design uses Cargo workspace inheritance. Put
Validation
All local results are at exact head 5458f181. The before state is its parent, main afc4be77.
| Check | Command | Result |
|---|---|---|
| The guard that this PR unblocks | python3 scripts/edge_release.py check-version --package-version <CLI package version> --stable-tag v0.15.0 |
afc4be77 (0.15.0): exit 1, "the package version 0.15.0 is not above the latest stable release v0.15.0". 5458f181 (0.15.1): exit 0. |
| Workspace versions | cargo metadata --locked --no-deps --format-version 1 |
Exit 0. All 22 packages report 0.15.1. |
| Lockfile scope | git show HEAD -- Cargo.lock |
Exactly 22 version lines change, one for each workspace package. No third-party entry changes. |
Remaining 0.15.0 outside release history |
git grep -F 0.15.0 -- ':!docs/releases' ':!changelog.d' ':!Cargo.lock' |
AGENTS.md:32 and docs/user/install.md:204 (item 2). docs/dev/documentation.md:286 is history and is correct. scripts/test_edge_release.py:114 is a test fixture. |
| Documentation | check-agents-md.sh, check-docs.py, test_release_notes.py, test_edge_release.py, release_notes.py preview --target HEAD, with the pinned scripts/requirements-docs.txt |
All pass. "Documentation OK (478 Markdown files checked)". The preview renders "Omnigraph v0.15.1". |
| Exact-head CI | gh pr checks 1320 |
28 checks pass, including Test Workspace (the CARGO_PKG_VERSION tests and the committed OpenAPI test). The 4 tag-only release jobs are skipped. |
| Other open PRs | Diffs of the other 36 open PRs | None adds a 0.15.0 pin or changes a version line, so this PR does not conflict with them. #1316 and #1317 add only a proptest dev-dependency. |
GQT does not apply: this PR fixes no bug and changes no query behavior. Lance is not affected.
Not done: a local build or test run (CI ran them at this commit), and cargo publish --dry-run. I make no claim about publication beyond what tag CI will check.
Opens the 0.15.1 cycle after the v0.15.0 release, as step 8 of the release checklist in
docs/dev/documentation.mddescribes.changelog.d/release.jsonnamesv0.15.1, withbaseset torefs/tags/v0.15.0,legacynull andformat2. Notes merged after the tag, such as those of perf(engine): write-allocate the dataset cache and hoist OCC validation out of the write gates #1291 and perf(engine):TableHandleCacheevicts under budget pressure, never at publish #1319, now belong to 0.15.1.Cargo.lockand the skill's version line updated to match. Edge builds are refused while the workspace version is not above the latest stable release.cargo metadata --locked,check-docs.pyandrelease_notes.py preview --target HEADpass.