Repository navigation
feat: v1.5.0 - Email notifications, Analytics dashboard, Alerts UX improvements - #13
Merged
Merged
Conversation
- GPU monitoring with multi-vendor support (NVIDIA, AMD, Intel) - Container-level CPU/memory breakdown metrics - Build cache efficiency tracking (Docker, Go, npm, Maven, Gradle) - Network egress cost estimation with tiered pricing - Agent self-update mechanism with version checking - Comprehensive test coverage for all new features
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 34547374 | Triggered | Generic Password | da177a3 | scripts/seed-demo.sh | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
- Use constant-time comparison to prevent timing attacks on API keys - Replace raw API key in cookies with random session tokens - Fix CORS: use allowlist instead of wildcard with credentials - Enable Secure cookie flag when HTTPS is detected - Add session token invalidation on logout - Add configurable RUNRIGHT_ALLOWED_ORIGINS env var
Tier 1 Enterprise Authentication: - Add goth multi-provider OAuth2/OIDC support - Google, GitHub, Azure AD, Okta built-in - Generic OIDC with auto-discovery - Add crewjam/saml for SAML 2.0 SSO - Database-driven provider configuration - Admin API for managing SSO providers - Domain allowlist for email validation - Role assignment on first login - Session management with secure tokens New endpoints: - GET /api/v1/sso/providers - list available providers - GET /api/v1/sso/login/:provider - initiate SSO flow - GET/POST /api/v1/sso/callback/:provider - handle callback - POST /api/v1/sso/logout - SSO logout - GET /api/v1/sso/me - current user info - GET/PUT/DELETE /api/v1/sso/configs - admin config management Environment variables: - RUNRIGHT_SSO_ENABLED - enable SSO authentication - RUNRIGHT_BASE_URL - base URL for OAuth callbacks - RUNRIGHT_SAML_CERT/KEY - X.509 cert for SAML SP
- Update LoginPage with SSO provider buttons - Fetch available SSO providers on mount - Display provider-specific icons (Google, GitHub, Azure, Okta, OIDC, SAML) - Add SSOSettingsPage for admin provider configuration - Add CRUD operations for SSO provider management - Add test configuration feature - Add setup documentation with callback URLs - Add SSO types and API functions - Add SSO navigation link in sidebar
…provements New Features: - Email notification destination (SMTP support with demo fallback) - Analytics dashboard with cost breakdown by repo/job/runner - Search bars for Alert Rules and Ownership tabs - Ownership form moved to top of tab for better UX - SSO improvements and enterprise features Backend: - EmailChannel adapter in notification package - SMTP config via RUNRIGHT_SMTP_* environment variables - Analytics API endpoints for cost trends and breakdowns - API keys management - Audit logging foundation - Team management endpoints Frontend: - Email tab in Destinations with subject prefix and recipients - Analytics page with charts and filters - Improved alert rules filtering - Ownership search functionality Docs: - Added CHANGELOG.md - Updated seed scripts for demo data
gbudjeakp
force-pushed
the
feature/tier3-agent-improvements
branch
from
July 4, 2026 21:51
65f74cf to
da177a3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v1.5.0
New Features
Backend
Frontend
See CHANGELOG.md for full details.