Julie v7.18.1
Patch release that re-pins julie-extractors from v2.27.0 to v2.34.3.
Julie remains retired as announced on 2026-07-28. This is another maintenance
drop on the final line so the extractor consumer stays current. Nothing further
is planned. Miller remains the supported
replacement.
Extractor Upgrade (v2.27.0 -> v2.34.3)
- Consumes the published v2.34.3 crate.
- Upstream classification is compatible: artifact schema, JSONL contract, and
family-store format are unchanged. The Rust public types Julie compiles
against (Symbol,Relationship, and the rest) are unchanged. EXTRACTION_CONTRACT_VERSIONis still byte-identical, so the
+extractors-tag=marker onSEMANTIC_INDEX_ENGINE_VERSIONis what forces
the rebuild.
Narrower test-role flags
Python, Scala, and Elixir is_test evidence is tighter, which reduces false
positives in ordinary source files:
- Python: decorator evidence is limited to
pytest.mark.*and the exact
unittest.skip/skipIf/skipUnless/expectedFailurenames.
pytest.fixtureandunittest.mock.*are not test evidence. Baretest_
names still require a test-path to count. - Scala:
@Test, lifecycle names, andtest-prefixed names remain
callable evidence. A test-directory path alone no longer marks helpers. - Elixir:
test_andtestnames remain callable evidence. Atest/
path alone no longer marks helpers.
A one-time reindex is forced
Existing workspaces re-index once on first run after upgrading. That is
deliberate: without the tag-marker bump, already-indexed files would keep
v2.27.0 is_test facts forever.
Runtime And Compatibility
- No Julie SQLite schema change.
- No external extract-contract change.
- No new languages.
- Manual MCP configs should still point at
julie-server.
Verification
cargo check --workspace --all-targets— clean- Pin contract tests RED→GREEN (
extractor_dependency_release_is_v2_34_3,
docs contract, engine-version tag guard) cargo xtask test bucket extractor-dep-integration— pass (3/3)cargo xtask test changed— 29 buckets pass
Upgrade notes
- The first index after upgrading is a full rebuild and takes proportionally
longer than an incremental update. No action is required. - Python / Scala / Elixir workspaces may show fewer
is_testflags on helpers
and fixtures that were previously over-marked.