fmql 0.3.0

Derive __version__ from package metadata (fmql 0.2.3, fmql-semantic 0…

….1.2) (#13)

Both packages had a hand-maintained `__version__` literal in `__init__.py`
that drifted from `pyproject.toml` — 0.2.2 shipped reporting `0.2.1` and
0.1.1 shipped reporting `0.1.0`. The stale fmql-semantic string was also
being baked into on-disk index metadata.

Switch `__version__` to `importlib.metadata.version(<pkg>)` so `pyproject.toml`
is the single source of truth. Update `test_version_cmd` to read the expected
value the same way — the previous hardcoded `"0.2.1"` literal is what hid the
drift in the first place.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Release fmql 0.2.2 + fmql-semantic 0.1.1 (#12)

- fmql: document `subgraph` command in README; add `--format {raw,cytoscape}`
  flag with Cytoscape.js-ready output shape
- fmql: extract duplicated `_json_default` helpers from cmd_query / cmd_cypher
  / cmd_subgraph / describe into a shared `fmql.serialization.json_default`
- fmql-semantic: formalize 0.1.1 CHANGELOG entries (env-publish for LiteLLM
  credentials, benign RuntimeWarning suppression)

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Derive __version__ from package metadata (fmql 0.2.3, fmql-semantic 0…

….1.2) (#13)

Both packages had a hand-maintained `__version__` literal in `__init__.py`
that drifted from `pyproject.toml` — 0.2.2 shipped reporting `0.2.1` and
0.1.1 shipped reporting `0.1.0`. The stale fmql-semantic string was also
being baked into on-disk index metadata.

Switch `__version__` to `importlib.metadata.version(<pkg>)` so `pyproject.toml`
is the single source of truth. Update `test_version_cmd` to read the expected
value the same way — the previous hardcoded `"0.2.1"` literal is what hid the
drift in the first place.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Release fmql 0.2.2 + fmql-semantic 0.1.1 (#12)

- fmql: document `subgraph` command in README; add `--format {raw,cytoscape}`
  flag with Cytoscape.js-ready output shape
- fmql: extract duplicated `_json_default` helpers from cmd_query / cmd_cypher
  / cmd_subgraph / describe into a shared `fmql.serialization.json_default`
- fmql-semantic: formalize 0.1.1 CHANGELOG entries (env-publish for LiteLLM
  credentials, benign RuntimeWarning suppression)

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

CI/publish: pin third-party actions to commit SHAs

Tags are mutable — SHAs aren't. Prevents a compromised upstream
action repo from retroactively injecting code into our release path.

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

Use shared pypi environment for semantic publish workflow

Consolidates both packages under one GitHub environment; PyPI trusted
publisher for fmql-semantic is configured with environment=pypi.

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

fmql 0.2.1

Replace LICENSE symlinks with real files in packages

Hatchling preserves symlinks in sdists, and Python 3.12+ tarfile
extraction refuses link-escape targets (e.g. ../../LICENSE -> /tmp/LICENSE),
which broke `python -m build` in the publish workflows.

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