release: v0.5.1 - security hardening (DEBT-024)

[fvadicamo]

What

v0.5.1 release: security hardening. Promotes develop to main.

Details

• DEBT-024 sweep (PR chore(security): dependency and CI security sweep (DEBT-024) #80): uv.lock re-lock closing 61 of 62 open Dependabot alerts, including the critical litellm authentication bypass; minimal permissions: blocks on all workflows (12 code-scanning alerts); admin login hardening closing the py/cookie-injection alert.
• Metrics migration: /metrics moved from starlette-prometheus (unmaintained, broken by starlette 1.x) to prometheus-fastapi-instrumentator (ARCH-014 updated).
• Dependency refresh: dev-deps group (chore(deps-dev): Bump the development-dependencies group across 1 directory with 9 updates #78), GitHub Actions checkout v7 (chore(deps): Bump actions/checkout from 6 to 7 #79) and paths-filter v4 (chore(deps): Bump dorny/paths-filter from 3 to 4 #39), esbuild 0.28 for the widget toolchain (chore(deps-dev): Bump esbuild from 0.25.0 to 0.28.1 in /vektra-learn/widget in the npm_and_yarn group across 1 directory #77).
• Release finalization (PR chore(release): finalize v0.5.1 #81): version 0.5.1 across 8 components, changelog, backlog bookkeeping.

The remaining open Dependabot alert (torch, low) has no patched release; tracked in DEBT-024 resolution notes.

Testing

• Full CI green on develop (unit per-component, integration + NFR gates, CodeQL, lint)
• 638 unit tests passed; integration verified on the PR chore(security): dependency and CI security sweep (DEBT-024) #80 cycle
• Widget build verified with esbuild 0.28

After merge

Tag v0.5.1 on the merge commit. No back-merge needed: the only main-side commit (esbuild bump #77) was reconciled into develop by PR #81.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@fvadicamo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5cce32b5-1919-485e-8cb8-9f660a0dc0f3

📥 Commits

Reviewing files that changed from the base of the PR and between c8696af and ca25717.

⛔ Files ignored due to path filters (5)

• .s2s/BACKLOG.md is excluded by !.s2s/**
• .s2s/CONTEXT.md is excluded by !.s2s/**
• .s2s/architecture.md is excluded by !.s2s/**
• .s2s/validation-scenarios.md is excluded by !.s2s/**
• uv.lock is excluded by !**/*.lock, !**/*.lock

📒 Files selected for processing (18)

• .github/workflows/ci-unit.yml
• .github/workflows/integration.yml
• .github/workflows/lint.yml
• .github/workflows/release.yml
• .github/workflows/shell-scripts.yml
• CHANGELOG.md
• pyproject.toml
• vektra-admin/pyproject.toml
• vektra-admin/src/vektra_admin/ui.py
• vektra-admin/tests/test_ui.py
• vektra-analytics/pyproject.toml
• vektra-app/pyproject.toml
• vektra-app/src/vektra_app/main.py
• vektra-core/pyproject.toml
• vektra-index/pyproject.toml
• vektra-ingest/pyproject.toml
• vektra-learn/pyproject.toml
• vektra-shared/pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gemini-code-assist]

Code Review

This pull request updates the project to version 0.5.1, focusing on security hardening and dependency updates. Key changes include replacing the unmaintained starlette-prometheus package with prometheus-fastapi-instrumentator for serving metrics, and hardening the admin login endpoint to prevent cookie injection by validating tokens against a urlsafe-base64 regex. The reviewer suggested extending the Prometheus instrumentator configuration to exclude health checks and documentation endpoints, which prevents internal polling traffic from polluting latency metrics.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.