Skip to content

fix: add SEARXNG_SECRET to CI fixtures and remove unused import#778

Merged
Lightheartdevs merged 1 commit intoLight-Heart-Labs:mainfrom
yasinBursali:fix/ci-fixtures-searxng-and-unused-import
Apr 3, 2026
Merged

fix: add SEARXNG_SECRET to CI fixtures and remove unused import#778
Lightheartdevs merged 1 commit intoLight-Heart-Labs:mainfrom
yasinBursali:fix/ci-fixtures-searxng-and-unused-import

Conversation

@yasinBursali
Copy link
Copy Markdown
Contributor

Summary

  • Add SEARXNG_SECRET to validate-env.yml CI fixture (fixes 5 tier validation failures)
  • Add SEARXNG_SECRET to test-validate-env.sh fixtures (fixes integration smoke failure)
  • Remove unused DASHBOARD_API_KEY import from extensions.py (fixes Ruff lint failure)

Context

PR #703 added SEARXNG_SECRET to .env.schema.json as required but missed updating CI
fixtures. Commit 7cfc606 switched agent auth from DASHBOARD_API_KEY to DREAM_AGENT_KEY
but left the stale import. These 3 issues cause 7 failing checks on every PR and on main.

Test plan

  • All 5 tier-N-env-validation checks pass
  • integration-smoke passes (test-validate-env.sh "Valid .env" test)
  • Python Lint / Ruff passes (no F401 unused import)

🤖 Generated with Claude Code

PR Light-Heart-Labs#703 added SEARXNG_SECRET to .env.schema.json as required but
missed updating the CI env fixtures — breaking all 5 tier validations,
the integration smoke test, and leaving the ruff lint red.

- Add SEARXNG_SECRET to validate-env.yml generated .env fixture
- Add SEARXNG_SECRET to test-validate-env.sh valid/unknown fixtures
- Remove unused DASHBOARD_API_KEY import from extensions.py (replaced
  by DREAM_AGENT_KEY in 7cfc606 but import was left behind)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Lightheartdevs Lightheartdevs merged commit 64276fc into Light-Heart-Labs:main Apr 3, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants