Changelog

New updates and improvements to Argos.

Enhanced batch progress visualization

Enhanced visualization of batch progress on the Argos build page

Argos now enriches your experience on the build page by displaying the progression of batches. This feature aims to provide immediate insights into the status of your builds, specifically highlighting if a build is pending due to a batch failure. It's designed to streamline your debugging process, ensuring you can quickly identify and address issues.

Furthermore, we've introduced detailed explanations for parallel builds marked as expired. This addition is geared towards offering clarity on your build's status, enhancing your ability to troubleshoot effectively.

Illustration showing a build aborted due to prolonged waiting time for all batches, with a detailed status of received 8/10 batches for nonce build-13.

Our commitment to improving your debugging experience remains unwavering. We believe these enhancements will significantly aid in your development workflow, making it more efficient and less error-prone.

GitHub Single Sign-On

GitHub SSO Settings in Argos Team

Introducing GitHub Single Sign-On (SSO) for Argos: Streamlining access and integration between your Argos team and your GitHub organization for improved security and seamless member synchronization.

Key Features

  • Seamless Integration: Connect your Argos team with your GitHub organization to sync membership automatically.
  • Easy Activation: Enable the GitHub SSO feature directly from your team settings with a simple "Enable and Pay" action.
  • Improved Security: Strengthen your team's access control with GitHub's authentication mechanisms.
  • Simple Deactivation: Disable the GitHub SSO feature at any time from your team settings.

GitHub SSO is available exclusively to Stripe subscribers at a cost of $50/month.

This feature is part of our commitment to providing powerful, secure tools for managing your Argos visual testing workflows. Enhance your team's management and security by enabling GitHub SSO today.

New changes trigger

Added and removed screenshot from Argos in GitHub commit status

We've listened to your input on how changes to screenshots within Argos should impact your workflow. With our latest update, Argos now treats the addition and removal of screenshots as diffs. This change ensures that any modifications to your visual assets are highlighted and require user approval, enhancing your control over visual consistency across your projects.

  • Added and removed screenshots in your repositories will now trigger an error status on GitHub and GitLab, drawing attention to visual changes.
  • These diffs will require manual approval from a user, ensuring that all visual changes are intentional and reviewed.
  • This update allows teams to maintain a high standard of visual quality and consistency, as any alterations to screenshots are explicitly flagged and reviewed.

This change is part of our ongoing commitment to providing powerful tools for visual testing, ensuring that Argos remains at the forefront of visual regression testing technologies.