Repository navigation
v1.0.4
igni-core 1.0.4
The first release published under igni's own name. igni-core on PyPI
is this repository's build: the igni_core module, the igni command
and the decisions service. The old name still installs it —
pip install ignite-ember resolves to igni-core==1.0.4 through the
alias (packages/ignite-ember/ — metadata, and a dependency on
igni-core at the same version), and the Homebrew formula
ignite-ember/tap/ignite-ember installs igni-core too, so nothing
that worked yesterday breaks.
It follows ignite-ember 1.0.3, the last release of the monolith
under the old name.
What a reader gets
pip install 'igni-core[decisions]==1.0.4'igni_core— the backend module. Theember_codename is gone;
igni_coreis the name every import uses now.igni— the command (ignite-emberis an alias for it, so old
shell aliases and the formula's link keep working). It runs one task
and exits:igni -m "…". There is no terminal chat UI — the chat is
the desktop app and the web client.igni-cloud— the cloud layer (PostgreSQL storage, the producer
and guest binding), in its own package, found through the
igni.layersandigni.storageentry points.
[decisions] adds igni's decisions service (Laya, torch), used by
Bypass mode's last check and by host.decide. Leave it out on a
backend that points IGNI_DECISIONS_URL at a shared one.
What changed
- The split. The backend is published under its own name, and the
cloud layer sits beside it inigni-cloudrather than inside it. - The wire contract is typed. The messages the backend and the app
exchange have one definition, checked from both sides: the app's
client is igni-core's contract, byte for byte. - One module per concern. The backend is split into modules that
each own one thing — settings, auth, the cloud, the tools, the
transport — behind interfaces the tests can substitute. Nothing
reaches into another's internals. igni login. A command, not a script: it opens the portal's
sign-in page in a browser, takes the token back over a local
callback, writes~/.igni/credentials.jsonand hydrates the group
pack.--token-stdindoes it without a browser.- The Windows sandbox is behind one interface. What it allows is
one thing to state, and one thing to test.
Upgrading
pip install --upgrade 'igni-core[decisions]==1.0.4'puts the new
backend in the same environment. The oldember_codepackage stays
where it was installed; nothing imports it any more.- The command is the new one:
igniandignite-emberboth point at
igni_core.__main__:mainafter the upgrade. - The desktop app installs this release itself, at the version it is
built for (igni-coreand the app share one version number), and
keeps an install made under the old name: the cache directory and
the install marker are still read under their old names until the
next write.
Verifying it
SHA256SUMS lists every file on the release. Each has GitHub build
provenance, a CycloneDX SBOM, and — when the signing key is present —
a cosign signature over the checksums. See
docs/VERIFYING_RELEASES.md.
Install
Python (CLI / library):
pip install 'igni-core[decisions]==1.0.4'
# or
uv pip install 'igni-core[decisions]==1.0.4'
# ``[decisions]`` adds igni's decisions service (Laya, torch) for
# Bypass mode's last check and ``host.decide``; leave it out on a
# backend that points IGNI_DECISIONS_URL at a shared one.Desktop app: released from
ignite-ember/igni-app
under the same version, which installs this backend on first launch.
Verify
SHA256SUMS lists every file on this release. Each one has
GitHub build provenance (gh attestation verify <file> --repo ignite-ember/igni-core; the bundle is attached for offline
checks), the *.cdx.json files are CycloneDX SBOMs, and
SHA256SUMS.sig, when present, is a cosign signature over the
checksums. See docs/VERIFYING_RELEASES.md.