153 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Xlorep DarkHelm	e539f9b0d8	ci: consolidate cicd workflow lanes, clean up helpers, and align CI docs (#86) ... ## Summary This PR simplifies the CICD workflow by merging related lanes, reducing duplicated script logic, and keeping the same overall pipeline behavior and gates. It also updates CI documentation to match the new job topology. ## What Changed ### Workflow consolidation - Merged base and complete CICD image publication into one producer job: - Build and Push CICD Images - Merged dependency audits into one informational lane: - Dependency Audits (Informational) - Merged runtime image build lanes into one release producer: - Build Release Images - Merged tester image build lanes into one tester producer: - Build Tester Images ### Dependency/gate rewiring - Updated downstream needs to consume merged producers. - Kept output contracts for deployable and tester image references. - Updated production and postmortem gates to the new job IDs. ### Cleanup/simplification - Removed duplicate helper-function definition(s) in CICD scripts. - Replaced a manual docker login retry loop with existing retry helper usage. - Removed redundant shell option declarations where behavior was unchanged. - Removed one unused E2E environment variable. ### Documentation alignment - Updated CI architecture documentation to reflect merged workflow lanes. - Updated troubleshooting guidance to reference current job sequencing. ## Why - Reduce job startup overhead on self-hosted runners. - Keep behavior consistent while lowering workflow complexity. - Improve maintainability by removing duplicated/unused script fragments. - Keep docs in sync with operational workflow reality. ## Validation - Workflow file checks passed with pre-commit. - Documentation checks passed with pre-commit (including markdownlint/prettier). - No diagnostics/errors reported for updated workflow/docs files. ## Risk and Impact - Low-to-medium operational risk due to job-ID/needs rewiring. - Mitigated by preserving output keys consumed by integration and e2e lanes. - Audit lane remains informational-only (non-blocking), same intent as before. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #86	2026-07-17 17:14:00 -04:00
Xlorep DarkHelm	19f6428775	ix runtime policy pin mismatch and make dependency audits non-blocking (#81) ... ## Summary This PR fixes backend test breakage caused by stale runtime compatibility pins and updates CI behavior so dependency audits remain informative without blocking delivery. ## What Changed - Updated backend runtime compatibility package pins to match current dependency versions. - Updated backend tests to align with the new compatibility expectations and restore coverage compliance. - Expanded backend unit coverage around runtime policy and health-check behavior. - Changed frontend and backend dependency audit lanes in CI to be non-blocking: - They still run in the same workflow position. - Failures are logged clearly. - Pipeline completion is no longer gated on audit pass/fail. ## Why - Recent dependency updates caused runtime policy startup validation to fail in tests. - Audit jobs are useful for visibility, but they should not prevent system completion when they detect issues. ## Validation - Pre-commit hooks passed on commit. - Backend unit tests with coverage pass, including fail-under threshold. - Branch pushed successfully: `fix/backend-runtime-policy-tests`. ## Notes - Audit failures now signal actionable dependency risk without stopping the release flow. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #81	2026-07-16 07:40:11 -04:00
copilotcoder	5fc16d4b5b	chore: run renovate on weekdays	2026-07-14 12:26:38 -04:00
copilotcoder	fdf8637f88	chore: reduce renovate log verbosity	2026-07-14 12:12:36 -04:00
copilotcoder	7603381c30	fix: harden renovate npm heap and dashboard approvals	2026-07-14 11:48:49 -04:00
copilotcoder	a2d7013dd4	chore: tune runner defaults and pin renovate to 8gb	2026-07-14 10:12:57 -04:00
copilotcoder	484bfbf74f	perf: harden renovate gitea api timeouts	2026-07-14 08:46:08 -04:00
copilotcoder	b5991ac1ae	perf: stabilize batched renovate runs	2026-07-14 07:55:01 -04:00
copilotcoder	e81f94c45c	perf: enforce renovate manager batching under 2gb cap	2026-07-14 07:35:03 -04:00
copilotcoder	7d053780f5	Patching the renovate flow. ... Signed-off-by: copilotcoder <copilotcoder@darkhelm.org>	2026-07-13 22:58:28 -04:00
Xlorep DarkHelm	f627ef018a	feat: integrate security audits into pre-commit and CI/CD with backend pip-audit migration (#74) ... ## Summary This PR integrates security-focused checks into the existing quality gates and aligns local workflows with CI/CD execution. ## What changed - Added Bandit to pre-commit backend checks. - Integrated eslint-plugin-security into the existing frontend ESLint setup used by pre-commit. - Added dedicated audit tasks: - backend audit via pip-audit - frontend audit via yarn npm audit - Updated CI/CD workflow to include and gate on frontend/backend audit jobs. - Switched backend vulnerability scanning from Safety to pip-audit to avoid interactive/auth requirements in CI. - Updated backend dependency set and lockfile to resolve test dependency conflicts and keep the environment solvable. - Marked backend integration API tests with the integration marker so marker-based unit/integration separation works consistently. ## Validation - Pre-commit hooks run and pass after formatting/autofixes. - Branch commit created successfully after hook-driven file updates. - Branch pushed to remote and tracking is configured. ## Notes - pip-audit now executes from backend context (for example via uv --directory backend run ...), matching project layout. - Remaining reported vulnerabilities depend on upstream package fix availability/constraints and may require follow-up once publishable fix versions are consumable. ## Follow-ups (optional) - Add a curated pip-audit ignore policy for non-actionable/transient advisories with rationale. - Open a focused follow-up PR for remaining dependency advisories once upstream fixes are practically installable. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #74	2026-07-13 22:19:57 -04:00
Xlorep DarkHelm	f3698b095b	Stabilize self-hosted CI workflows and resolve issue #62 (#73) ... ## Summary Hardens CI workflows for self-hosted Gitea runners by stabilizing E2E execution and Renovate behavior across internal/external network paths. Closes #62 ## What Changed ### E2E workflow reliability - Fixed E2E workspace handoff to ensure expected repository contents are present during test execution. - Added stricter preflight checks for required frontend files before running E2E. - Reduced mount/path fragility while preserving runtime image pull and compose flow. ### Renovate workflow hardening - Added internal-first endpoint reachability selection with fallback handling. - Added token preflight checks for repository access. - Added explicit host-rule auth handling for API/git paths. - Added container-level connectivity preflight diagnostics. - Added git URL override aligned with selected endpoint context. - Removed incorrect forced Dogar host-IP pinning that broke HTTPS clone routing. ## Why CI behavior was sensitive to runner networking and Renovate clone/auth interactions. These changes make the workflow deterministic in our runner topology and address recurring CI failures. ## Scope - Workflow logic only (`cicd.yaml`, `renovate.yml`) - No app feature or API behavior changes ## Validation - Workflow YAML validation passed during updates. - Changes were applied and verified iteratively from real failing run diagnostics. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #73	2026-07-13 11:16:16 -04:00
Xlorep DarkHelm	1f6cafa1bc	TASK: Replace integration lane with post-build backend runtime black-box tests (#72) ... ## Summary Replace the existing source-context integration lane with backend runtime black-box integration checks that run against started deployable containers. This change wires deployable backend image references (both commit tag and immutable digest) from the build workflow into the tests workflow, then validates runtime behavior over network endpoints. ## Why Integration confidence should come from testing running service artifacts, not only source-mounted or in-process execution. ## What Changed - Build workflow now: - Publishes deployable backend image tag reference and digest reference - Exposes both as job outputs - Passes both references into CICD Tests dispatch inputs - CICD Tests workflow now: - Accepts deployable backend tag and digest inputs - Propagates these through setup outputs - Replaces previous integration lane behavior with runtime black-box execution: - Starts isolated Docker network - Starts Postgres container - Starts backend container from digest-pinned deployable image - Enforces tag-to-digest consistency before running checks - Runs endpoint checks against live container: - GET / - GET /compatibility - GET /health - Captures backend/db logs and container state on failure - Cleans up containers and network via trap - Documentation updated: - Runtime contract enforcement section now includes runtime black-box integration checks - CI success summary now reflects runtime integration lane behavior ## Scope Included: - Backend runtime black-box integration replacement for the existing integration lane - Digest + tag identity enforcement - Failure diagnostics for triage Out of scope: - Frontend runtime smoke checks - E2E lane redesign ## Acceptance Criteria Mapping - Integration tests execute against runtime container endpoints: ✅ - Integration lane consumes built image references (not source-mounted execution): ✅ - Failures surface service logs and test logs for triage: ✅ ## Verification - Workflow files pass local validation checks - Pre-commit hooks pass on committed changes - Branch pushed and ready for PR review ## Related - Issue: #61 - Dependency context: #66 Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #72	2026-07-05 22:48:57 -04:00
Xlorep DarkHelm	549469f105	CI: Establish source-first quality gate and simplify pipeline flow (#71) ... This PR establishes a deterministic source-level quality gate before any build promotion and removes redundant post-build quality checks. The new flow makes local developer workflow and CI behavior align: - Developers run pre-commit locally (with auto-fix where appropriate) - CI runs a check-only smoke gate to validate pre-commit cleanliness - Build/test promotion only proceeds after source checks pass ## What Changed ### 1. Added a source-first quality gate - Added a dedicated source gate workflow: - `.gitea/workflows/cicd-source-checks.yaml` - Gate now: - Checks out target SHA - Bootstraps backend/frontend toolchains - Installs dependencies (`backend` via `uv`, `frontend` via `yarn`) - Runs `pre-commit --all-files` as the quality smoke test - Downstream build dispatch only occurs if this gate passes. ### 2. Updated pipeline routing - `cicd-start.yaml` now dispatches the source gate first. - `cicd-start.yaml` push trigger now includes all branches so feature branches run the same gate. - Added explicit routing logs in dispatch steps (route decision, SHA, trace id) for easier debugging. ### 3. Removed redundant checks workflow - Removed: - `.gitea/workflows/cicd-checks.yaml` - Updated: - `.gitea/workflows/docker-build-main.yaml` now dispatches `cicd-tests.yaml` directly after successful main build. ### 4. CI check-only behavior vs local auto-fix behavior Updated `.pre-commit-config.yaml` so hooks that can auto-fix behave as: - **Local developer pre-commit**: auto-fix enabled - **CI source gate**: check-only (no auto-fix) Applied to: - `ruff` / `ruff-format` - `eslint` - `prettier` - `tsdoc-lint` - `markdownlint` - `pretty-format-toml` This keeps CI as a true smoke validation of local pre-commit compliance. ### 5. Renovate workflow hardening - Improved auth/token handling and diagnostics in: - `.gitea/workflows/renovate.yml` - Added support for internal/self-signed TLS endpoints used by this environment. ## Why - Faster, earlier feedback on source quality failures - Avoid expensive build/test progression when source hygiene fails - Align CI with developer habits for predictable outcomes - Remove duplicated quality checks and reduce pipeline complexity ## New Effective CI Flow 1. `cicd-start.yaml` 2. `cicd-source-checks.yaml` (pre-commit smoke gate) 3. `docker-build-base.yaml` / `docker-build-main.yaml` 4. `cicd-tests.yaml` ## Acceptance Criteria Mapping (Issue #60) - Source-level lane runs independently and consistently: **Implemented** - Source-lane failure blocks promotion: **Implemented** - Outputs/logging are clear and actionable: **Implemented** ## Notes - Source gate is intentionally check-only in CI. - Developers should continue running local pre-commit before pushing. - Any remaining failures in source gate indicate local pre-commit was not fully clean. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #71	2026-07-02 07:21:18 -04:00
Xlorep DarkHelm	b16ef3a276	Minor adjustments to renovate. (#70) ... Signed-off-by: copilotcoder <copilotcoder@darkhelm.org> Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #70	2026-06-22 12:56:59 -04:00
Xlorep DarkHelm	c7540e97ad	feat(ci): enforce runtime-validation image separation (#69) ... ## Summary Implements issue #59 by enforcing a hard boundary between CI validation tooling and deployable runtime images. This PR: - Adds automated deployable-runtime boundary checks in CI. - Verifies deployable backend/frontend artifacts are free of CI/development tooling. - Documents runtime-vs-validation ownership and enforcement behavior. ## What Changed ### CI workflow enforcement - Updated `.gitea/workflows/docker-build-main.yaml` to: - Checkout additional verification inputs (`Dockerfile.backend`, `Dockerfile.frontend`, scripts, backend/frontend directories). - Run `scripts/check-dockerfile-boundaries.sh`. - Build deployable runtime images (`Dockerfile.backend`, `Dockerfile.frontend --target production`). - Run `scripts/verify-deployable-image-purity.sh` against both images before publishing CICD image. - Updated `.gitea/workflows/cicd-checks.yaml` to add: - `dockerfile-boundary-check` job. - Boundary validation execution inside the CICD validation image. ### New enforcement scripts - Added `scripts/check-dockerfile-boundaries.sh`: - Ensures deployable Dockerfiles do **not** reference CICD image paths (`cicd-base`, `CICD_BASE_IMAGE`, `Dockerfile.cicd*`, etc.). - Ensures deployable Dockerfiles do **not** include disallowed CI-only tooling tokens. - Enforces runtime base expectations: - Backend: `python:3.14-slim` - Frontend production target: `nginx:alpine` - Added `scripts/verify-deployable-image-purity.sh`: - Baseline binary checks for disallowed tooling. - Backend-specific deep checks: - Python module import probes for disallowed CI/dev modules. - `pip show` package metadata checks for disallowed CI/dev packages. - Frontend-specific deep checks: - OS package metadata checks (`apk`/`dpkg` when available) for disallowed runtime leaks. - Directory-based checks for development package trees (`node_modules`, `.venv`, `site-packages`, `dist-packages` in sensitive paths). ## Documentation updates - Updated `docs/DEVELOPMENT.md`: - Clarifies runtime-vs-validation enforcement and where checks run. - Notes purity checks include binaries and metadata artifacts. - Updated `docs/CICD_MULTI_STAGE_BUILD.md`: - Adds explicit “Runtime Boundary Enforcement” section. - Documents metadata-level purity probes. - Updated `docs/DEPLOYABLE_RUNTIME_CONTRACT.md`: - Replaces future-only language with current enforcement hooks. - Documents binary + metadata-level purity enforcement. ## Acceptance Criteria Mapping 1. **Deployable backend/frontend image paths do not require CI-only tool installation** - Enforced by: - `scripts/check-dockerfile-boundaries.sh` - `scripts/verify-deployable-image-purity.sh` - `docker-build-main.yaml` pre-publish gates 2. **Checks and tests execute in dedicated validation environment(s)** - Reinforced by: - `cicd-checks.yaml` boundary-check job running in CICD validation image - Existing check/test workflow usage of CICD image 3. **Workflow docs identify runtime vs validation concerns** - Addressed via updates to: - `docs/DEVELOPMENT.md` - `docs/CICD_MULTI_STAGE_BUILD.md` - `docs/DEPLOYABLE_RUNTIME_CONTRACT.md` ## Scope / Non-Goals - Included: - Structural separation enforcement - Workflow-level guardrails - Documentation clarity and traceability - Not included: - Full staging deployment wiring - Security policy redesign ## Notes for Reviewers - Main enforcement path is in `docker-build-main.yaml` before CICD image publish. - New scripts are intentionally fail-fast and policy-oriented. - Existing deployable Dockerfiles currently satisfy the new gates. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #69	2026-06-22 12:45:20 -04:00
Xlorep DarkHelm	9b742a5a6d	feature/pp-58-runtime-image-contract (#68) ... ## Summary This PR tightens repository quality enforcement around markdown and documentation. It adds `markdownlint` to the `cicd-checks` workflow, expands pre-commit coverage so markdown files are checked repo-wide, and cleans up the PP-58 documentation set to keep it aligned with the new policy. ## What changed - Added a `Markdownlint Check` entry to `.gitea/workflows/cicd-checks.yaml` - Added `markdownlint` to pre-commit and widened prettier coverage to include markdown files across the repo - Updated `README.md` to satisfy markdownlint line-length rules - Normalized the PP-58 documentation set: - `docs/DEPLOYABLE_RUNTIME_CONTRACT.md` - `docs/adr/ADR003-deployable_runtime_image_contract.md` - `docs/DEVELOPMENT.md` - `docs/CICD_MULTI_STAGE_BUILD.md` - `docs/CICD_TROUBLESHOOTING_GUIDE.md` - `docs/SECURE_DOCKER_CICD.md` ## Validation - `pre-commit run markdownlint --files README.md docs/DEPLOYABLE_RUNTIME_CONTRACT.md` - `pre-commit run prettier --files README.md docs/DEPLOYABLE_RUNTIME_CONTRACT.md` - Workflow YAML validation returned no errors ## Notes This change does not alter application runtime behavior. It only strengthens CI and documentation quality enforcement. Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #68	2026-06-19 17:00:57 -04:00
Xlorep DarkHelm	48a37b943f	PP-11_Add_SQLAlchemy_async_engine_session (#67) ... ## Summary This PR upgrades backend typing tooling and finalizes quality cleanup for the SQLAlchemy async engine/session work on `PP-11_Add_SQLAlchemy_async_engine_session`. ## What Changed - Upgraded pinned `pyright` version from `1.1.406` to `1.1.410`. - Regenerated backend lock state to align with the new pyright pin. - Removed deprecated `pythonPath` from pyright config to eliminate the config notice. - Refined backend DB runtime state handling and cleanup paths. - Updated database tests to avoid brittle singleton assumptions and keep typeguard-compatible async engine test doubles. ## Why - Remove tooling noise and keep checks deterministic. - Keep backend static/type/doc/test quality gates warning-free. - Improve reliability and clarity of DB engine/session lifecycle tests. ## Validation - `uv run ruff format --check .` - `uv run ruff check .` - `uv run pyright .` - `uv run pydoclint --config=pyproject.toml src/` - `uv run xdoctest --module backend` - `uv run pytest` Results: - Pyright: `0 errors, 0 warnings` - Pytest: `21 passed` ## Impact - No API contract changes intended. - No frontend changes. - Backend behavior remains the same; this is tooling/test/runtime-state cleanup. ## Risk - Low risk. - Main touched areas are backend tooling config, lockfile, DB runtime state internals, and tests. ## Checklist - [x] Backend lint clean - [x] Backend type checks clean - [x] Backend doc checks clean - [x] Backend tests passing - [x] Branch pushed and ready for review Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #67	2026-06-19 07:39:56 -04:00
Cliff Hill	d02039a22e	Backend runtime upgraded to Python 3.14 with exact dependency pinning (#57) ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org> ## Summary Upgrades backend runtime baseline and dependency management for issue #10. ### Changes 1. **Python Baseline**: Updated from 3.13 to 3.14 - Updated `backend/pyproject.toml` requires-python constraint - Updated `backend/pyrightconfig.json` pythonVersion - Updated all Dockerfile and CI references 2. **Dependency Pinning**: Switched to exact version pins in `backend/pyproject.toml` - All dev and runtime dependencies now use `==` instead of `>=` - `fastapi==0.120.2`, `uvicorn==0.38.0` - ruff, pyright, pytest suite pinned to current resolved versions - Regenerated `backend/uv.lock` under Python 3.14 3. **Startup Compatibility Guard** (TDD via RED→GREEN) - New `compatibility_status()` function evaluates runtime and pinned deps - Startup raises `RuntimeError` if policy fails - Implemented via FastAPI lifespan (non-deprecated) handler 4. **Compatibility Status Endpoint** - New `GET /compatibility` returns policy status, runtime version, and package checks - Shares single source of truth with startup validation 5. **Integration Tests** - Added failing-then-passing tests for startup guard and endpoint behavior - 100% coverage maintained 6. **Direnv Configuration** - Added `UV_PYTHON="3.14"` pin to repo `.envrc` - Ensures direnv creates/recreates venv with correct Python version ### Validation - ✅ ruff format/check - ✅ pyright strict (0 errors) - ✅ pytest: 8 passed, 100% coverage (>=95 gate) - ✅ pydoclint: pass - ✅ xdoctest: pass ### Notes - SQLAlchemy/SQLModel introduction deferred to next pass per scope - Compatibility logic currently validates fastapi/uvicorn pins (runtime deps) - Ready for container build validation and Renovate bot testing Co-authored-by: copilotcoder <copilotcoder@darkhelm.org> Reviewed-on: #57 Co-authored-by: Cliff Hill <xlorep@darkhelm.org> Co-committed-by: Cliff Hill <xlorep@darkhelm.org>	2026-06-18 11:19:24 -04:00
Cliff Hill	5d74dd8d8f	Adding some stuff for the new structure to work with my system. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2026-04-08 09:45:49 -04:00
Cliff Hill	18dc1c887a	Retrying run.	2025-11-06 08:22:48 -05:00
Cliff Hill	d3a839489e	Retrying run.	2025-11-06 08:22:45 -05:00
Cliff Hill	e401d852f4	Fixing renovate (again). ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-06 07:09:55 -05:00
Cliff Hill	de5fde5460	Trying this again.	2025-11-05 18:10:10 -05:00
Cliff Hill	4454e9aef5	Adding renovate stuff. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-04 12:40:53 -05:00
Cliff Hill	a142bc46c2	CICD workflow is now valid. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-03 12:14:44 -05:00
Cliff Hill	b9c6b604b1	Make the e2e test use docker in the same way all the others do. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-03 08:40:19 -05:00
Cliff Hill	bf1f3f30df	Making the e2e tests more resiliant for network issues. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 18:33:19 -04:00
Cliff Hill	e16141cdbd	Better dependency processing for the frontend in the CICD. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 16:13:30 -04:00
Cliff Hill	125e889501	Even more dependency fixing happening here. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 15:24:59 -04:00
Cliff Hill	9203e4ff73	More frontend dependency fixes for the CICD build. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 13:27:56 -04:00
Cliff Hill	c34c6e45d6	Adding CICD troubleshooting documentation. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 13:04:39 -04:00
Cliff Hill	b0115e33d3	Attempting to fix how the frontend dependencies are handled in the CICD build. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 13:03:18 -04:00
Cliff Hill	91e6dd7ae1	Fixing the build. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 12:45:11 -04:00
Cliff Hill	aee570e8c3	Trying to improve how images are built, using docker caching the best I can ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 11:20:56 -04:00
Cliff Hill	570bc83295	Making it more resiliant to network problems, fixing playright ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 10:47:02 -04:00
Cliff Hill	941106d59a	Fixing playright again ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-11-01 00:20:31 -04:00
Cliff Hill	a9db4d64bc	Fixing playright ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 22:39:31 -04:00
Cliff Hill	6747b03957	More CICD image fisex, part 2 ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 18:42:23 -04:00
Cliff Hill	728cebcca2	More CICD image fixes ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 15:37:54 -04:00
Cliff Hill	cad7c7fea9	Fixing how uv is being used in the base image, adding Poe the Poet to everything. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 13:25:03 -04:00
Cliff Hill	772c4cfab5	Fixing the optimization ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 12:48:40 -04:00
Cliff Hill	9bbb362e5b	Optimizing the docker builds for cicd. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 11:25:34 -04:00
Cliff Hill	0399446a7e	Trying to make sure the two sides of the image play nicely together. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 10:03:17 -04:00
Cliff Hill	6df52238de	Optimizing the build so that CICD doesn't take FOREVER to run. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-31 09:09:46 -04:00
Cliff Hill	c5660e547a	Trying to make e2e be truly non-interactive and headless. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-30 22:32:59 -04:00
Cliff Hill	aee066d611	Fixing the e2e tests (again). ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-30 18:47:47 -04:00
Cliff Hill	10c6fa33c9	Fixing the e2e tests. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-30 16:24:21 -04:00
Cliff Hill	f29cd0f633	Documentation updates. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-30 16:21:02 -04:00
Cliff Hill	eb8802eea2	Fixing frontend coverage. ... Signed-off-by: Cliff Hill <xlorep@darkhelm.org>	2025-10-30 14:15:13 -04:00