Skip to content

Releases: juzcn/local-embed

Release list

local-embed 0.3.1

local-embed 0.3.1 Latest
Latest

Choose a tag to compare

View all tags
@juzcn juzcn released this 14 Oct 11:41
v0.3.1
1ea62a8

Documentation correction; no code changes.

The READMEs described the config-path precedence as $LOCAL_EMBED_FILE > slife project root (dev) > ~/.local-embed/local_embed.yaml. The dev-mode step was removed in 0.3.0 — resolve_config_path() never consults the working directory — so the READMEs now state the two-step precedence, and note that a host wanting the config beside its own must export $LOCAL_EMBED_FILE. Slife seeds ~/.local-embed/local_embed.yaml and relies on the default, so nothing changes for it.

Assets 2
Loading

local-embed 0.3.0

local-embed 0.3.0

Choose a tag to compare

View all tags
@juzcn juzcn released this 13 Oct 13:42
v0.3.0
1e18f31

First release from this standalone repository (PyPI's previous newest was 0.2.4).

Extracted from the local-embed/ subdirectory of Slife. Slife remains its primary host — it spawns local-embed and exports $LOCAL_EMBED_FILE — but the package is now developed, documented and released from its own repository. Installer URLs, pyproject metadata and the README's "re-adding a backend" section (which now targets the local-embed tool venv rather than slife's) all point here.

Behaviour change

The is_slife_dev() dev-mode config override is gone. resolve_config_path() is now $LOCAL_EMBED_FILE > ~/.local-embed/ and no longer consults the working directory. A host that wants the config beside its own already exports $LOCAL_EMBED_FILE, so the CWD rule could only ever produce a second, silently different answer for the same machine.

If you ran local-embed by hand from a Slife checkout, point $LOCAL_EMBED_FILE at that local_embed.yaml to keep the old behaviour.

Changed

  • The installers and both READMEs pass --python '>=3.13' to uv tool install, so uv fetches a suitable interpreter instead of leaving the tool environment without a compatible release.

Fixed (documentation)

  • The README no longer claims the installers preserve a manually added backend across an upgrade. They do not: uv tool install --force rebuilds the tool environment, so the backend is dropped.
  • The README referenced a LICENSE that did not exist; it is now committed.

Added

  • uninstall.sh / uninstall.ps1, a README.zh-CN.md translation, and ruff/pyright as dev dependencies. CI runs the suite on Windows, macOS and Linux plus lint and type-check jobs.
Loading