~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.
Python academiaanthropicarxivbravedeep-researchencryptionhome-automationhomeserverlocallocal-deep-researchlocal-llmmistralollamaopenaipubmedresearchresearch-toolretrieval-augmented-generationsearxngself-hosted
docs(release): correct the retention comment — effective window is 5 days, bounded by SLSA provenance (#5035)
LearningCircuit09b0b2dcead9
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex a8799521c1..51bde08df8 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -477,9 +477,15 @@ jobs:# came ~30h later, failing create-release with "Artifact not# found" and leaving the release unrecoverable (the signed SBOM# bytes referenced by the SLSA provenance subjects were gone).- # 7 matches prerelease-docker.yml's sbom artifact and survives a- # weekend-delayed approval; a re-run of a failed create-release- # also stays possible for a week.+ #+ # NOTE: the EFFECTIVE window for approving (or re-running a+ # failed) create-release is 5 days, not 7 — the provenance job+ # (also pre-approval) uploads provenance.intoto.jsonl inside the+ # SLSA generator reusable workflow, which hardcodes+ # retention-days: 5 with no caller input to change it (verified+ # at the pinned v2.1.0 commit). 7 here just keeps THIS artifact+ # from ever being the binding constraint; if the generator gains+ # a retention input, align both values.retention-days: 7# Generate SLSA provenance for release artifacts