v0.3.30
Latest Release

Added

  • bugster config command - Access and manipulate the data inside config.yaml to avoid human error
    • --bypass-protection flag: Guides users on how to get the x-vercel-bypass-secret by redirecting them with the Deeplink
  • bugster install command - Handle outside integrations with your Bugster account for users who don’t want to switch context during setup
    • --github flag: Redirects users to the Github App Installation Link

Changed

  • Destructive Agent Limits - Up to 4 as default, with future parametrization based on subscription tiers
  • Prioritization of UI crashers instead of Form Destroyers (FD will run when all UI Crashers are ok)
v0.3.26
Authentication & Parallel Execution

Added

  • bugster auth command for setting up or cleaning existing API key
  • --parallel flag for bugster run command (accepts both --parallel and --max-concurrent)

Changed

  • Max test limit increased to 10
v0.3.25
Platform Flags

Changed

  • Added platform flags to bugster init for faster setup
v0.3.24
Automatic Execution

Changed

  • Added flags to bugster init for executing automatically
v0.3.23
Bug Fixes

Fixed

  • Patch update command
v0.3.22
Destructive Architecture

Changed

  • New architecture for bugster destructive unblocking longer executions
v0.3.21
Monorepo Support & Generation Improvements

Added

  • Initial monorepo support
    • Works with most monorepo setups including basic Turborepo configurations
    • Detects changes in individual apps within the monorepo
    • Note: Currently does not track changes in shared packages (e.g., common components installed via pnpm in each app’s node_modules)

Changed

  • bugster generate default settings - Can be executed multiple times without adding --force explicitly
  • Improved test generation intelligence - Both bugster generate and bugster update now analyze existing test specs context to avoid creating duplicate or similar tests
v0.3.20
Installation Improvements

Changed

  • Force chromium installation on install script
  • Remove the question loop on credentials during bugster init
v0.3.19
Page Flag Enhancement

Changed

  • Enhanced --page flag in bugster generate now accepts relative or absolute file paths instead of page folder names
  • Added validation for the --page flag to ensure provided paths exist, are files, and have valid JavaScript/TypeScript extensions (.js, .jsx, .ts, .tsx)
v0.3.15
Performance & Control Features

Added

  • --stream-results as the default behaviour for bugster run
  • --max-concurrent = 5 as the default behaviour for bugster run
  • --page flag for bugster generate for spec generation of specific pages
  • --count option for bugster generate to control the number of test specs generated per page (min: 1, max: 30)
v0.3.14
Vercel Protection Bypass

Added

  • Vercel protection bypass to bugster destructive
v0.3.13
Test Run Association

Added

  • run_id to bugster destructive for test run association
v0.3.12
Destructive Agent

Added

  • bugster destructive - Our new agent for raising bugs
v0.3.11
Preferences & Always Run

Added

  • preferences section to the configuration file
  • always_run option to select up to 3 specs that will always run
v0.3.10
Performance Improvements

Changed

  • Improved bugster generate architecture resulting in a 30% speed increase
v0.3.9
Vercel Bypass Automation

Added

  • Vercel-bypass-automation support - You can now use the secret within Bugster config while keeping your branch protected
v0.3.7
Enhanced Generation Capacity

Added

  • Enhanced bugster generate specs generation capacity up to 20 specs for comprehensive coverage

Changed

  • Improved specs generation algorithm for better coverage and more realistic test scenarios
v0.3.6
Issues & Upgrade Commands

Added

  • bugster issues command to get failed runs with debugging context from recent executions
  • bugster upgrade command to update CLI to the latest version directly from the command line

Changed

  • Improved specs generation algorithm for better coverage and more realistic test scenarios

Fixed

  • Small bug in the console message during bugster init
v0.3.0
Major Release - Affected Tests & Parallel Execution

Added

  • --only-affected flag for bugster run to execute only specs affected by code changes
  • --max-concurrent flag for bugster run supporting up to 5 parallel test executions
  • Component-level tracking for bugster update command
  • GitHub integration for running specs on Vercel preview deployments
  • Cross-platform installer scripts for Windows, macOS, and Linux with automatic dependency management

Changed

  • Enhanced bugster update command now works at component granularity instead of file level
  • Improved parallel test execution with better resource management
  • Optimized change detection algorithm for more accurate affected test identification
  • Rich console output with color-coded messages and progress indicators
  • Enhanced error handling with detailed debugging information

Fixed

  • Performance improvements for large codebases with many components
  • Better handling of component dependency tracking
  • Reduced false positives in change detection
v0.2.0
Sync, Auth & Update Commands

Added

  • bugster sync command to retrieve and manage test specs across different branches
  • bugster auth command for secure API key management with GUI integration
  • bugster update command to automatically update test specs when codebase changes
  • Project creation integration with Bugster GUI dashboard for execution tracking
  • Branch-based specs synchronization

Changed

  • Enhanced bugster init command now creates projects in the GUI dashboard

Fixed

  • Authentication improvements
  • Project initialization reliability
  • Cross-branch synchronization edge cases
v0.1.0
Initial Release

Added

  • Initial CLI commands: bugster init, bugster generate, and bugster run
  • Next.js application support with automatic framework detection
  • Test specs generation (up to 5 test specs per application)
  • Basic test execution engine with browser automation
  • Project configuration system with YAML-based config files
  • Core specs format and parsing capabilities