July Product Update

July was an action-packed month for Viraza, with a whopping 172 pull requests merged. Key highlights include significant improvements in API error handling, UI enhancements for permission management, and a streamlined deployment process. We also focused on performance tweaks, especially with our database interactions and CI workflows. With thorough documentation updates, our users can better navigate the new features and fixes. Dive in to see the highlights of what we achieved this month.

Features

• Enhanced API Functionality

  feat: v2/keys.deleteKey - Introduced a new endpoint for deleting keys, expanding our API capabilities.

  feat: onboarding - Launched the first part of our new onboarding UI, making it easier for users to get started.

  feat: v2/keys.updateCredits - Added an endpoint to update credits, improving user experience.

• UI Improvements

  feat: onboarding key creation - Introduced a new step in the onboarding process for key creation.

  feat: Initial implementation of Viraza Deploy - Launched core services for our deployment platform.

Bug Fixes

• Critical Bug Fixes

  fix: calendar bug - Resolved an issue with date selection in the calendar UI, enhancing user experience.

  fix: merge issues - Fixed various merge conflicts that were causing issues in the codebase.

  fix: non null assertion linter issues - Addressed linter issues to improve code quality.

Performance

• Optimized Performance

  perf: create root key being slow - Enhanced the performance of root key creation, reducing wait times.

  perf: use namespace_id as index - Improved database query performance by optimizing index usage.

Documentation

• Documentation Updates

  fix: documentation manual ratelimit example missing fields - Updated documentation to ensure all fields are clearly defined.

  chore: reorganise engineering docs and add runbooks - Streamlined the documentation structure for better accessibility.

Chores

• Maintenance and Refactoring

  chore: remove unused dependencies - Cleaned up the codebase by removing unnecessary dependencies.

  chore: use makefiles - Transitioned from Taskfiles to Makefiles for better build automation consistency.

  chore: delete unnecessary tests - Removed obsolete tests to maintain a cleaner codebase.