Skip to content

v0.1.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 May 04:32
v0.1.4
50c6038
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[0.1.4] — 2026-05-04

Two install-path bug-fixes plus a docs note for the third — all surfaced
by a real user trying to install behind a corporate proxy.

Fixed

  • internal/config/config.go now binds every defaulted key to its
    DOCSIQ_<UPPER_KEY> env variant via a single
    for _, key := range v.AllKeys() { _ = v.BindEnv(key) } after defaults
    are set. Previously only ~9 keys were explicitly bound, which meant
    DOCSIQ_LLM_PROVIDER, DOCSIQ_LLM_OLLAMA_CHAT_MODEL,
    DOCSIQ_LLM_AZURE_*, DOCSIQ_LLM_OPENAI_*, DOCSIQ_DATA_DIR,
    DOCSIQ_INDEXING_*, etc. were silently ignored when no config file was
    present (Viper #761 — AutomaticEnv + Unmarshal doesn't see env-only
    keys without explicit BindEnv). The existing explicit BindEnv calls
    for server.api_key, workq_workers, etc. are retained — they
    document the secondary DOCSIQ_API_KEY alias and harmlessly
    double-bind. (#95)

Added

  • internal/config/config_test.go — TestLoad_EnvOverridesLLM regression
    test that asserts DOCSIQ_LLM_OLLAMA_CHAT_MODEL,
    DOCSIQ_LLM_OLLAMA_EMBED_MODEL, DOCSIQ_LLM_PROVIDER,
    DOCSIQ_LLM_AZURE_API_KEY, and DOCSIQ_DATA_DIR all reach the
    populated *Config struct without a config file present. (#95)

Changed

  • docs/getting-started.md "Install" section now uses
    GOFLAGS='-tags=sqlite_fts5' go install github.com/RandomCodeSpace/docsiq@latest
    with an explicit explanation that the build tag is required because
    docsiq uses SQLite's FTS5 extension via mattn/go-sqlite3 — without
    it the binary fails at runtime with unable to open store: no such module: fts5 when opening any project DB. (#95)

Known limitations

  • go install does not produce a working web UI. docsiq's React UI
    is embedded via //go:embed ui/dist, but the ui/dist/ build outputs
    are intentionally gitignored — only a placeholder index.html is
    committed. The release pipeline runs npm run build before go build,
    so the prebuilt release binaries on this page have the full UI
    baked in. A go install build, by contrast, embeds only the
    placeholder index.html and hits 404 on every /assets/* request.
    For docsiq serve use cases, install via
    gh release download v0.1.4 --repo RandomCodeSpace/docsiq --pattern 'docsiq-*-linux-amd64*'
    (or your platform's equivalent asset). The CLI commands
    (docsiq index, docsiq version, docsiq projects, etc.) work
    correctly on a go install build; only the embedded UI is affected.
    Tracked as a follow-up.

Upgrade impact

Drop-in for the test suite and config layer. Previously-ignored env
vars are now honoured — if you had DOCSIQ_LLM_* or
DOCSIQ_INDEXING_* set in a shell or CI environment, those values
will now reach docsiq where they were silently dropped before. Audit
your environment for unintended DOCSIQ_* settings before deploying.

Verify

All artifacts are signed with cosign keyless via Sigstore.

cosign verify-blob \
  --certificate-identity-regexp 'https://github.com/RandomCodeSpace/docsiq/\.github/workflows/release\.yml.*' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  --certificate docsiq-v0.1.4-linux-amd64.pem \
  --signature docsiq-v0.1.4-linux-amd64.sig \
  docsiq-v0.1.4-linux-amd64
Assets 13
Loading