Introducing deployment hooks

GitPeeks now supports deployment hooks, allowing you to run custom logic at different stages of the deployment process—perfect for setup, cleanup, or notifications.

🚀 What’s new?

You can now define hooks for your preview developments. These hooks let you automatically run custom scripts or logic during deployments—for example, loading test data or sending notifications.

🤔 Why did we make this change?

Teams often need to perform specific actions around deployments, and doing that manually adds friction and risk. With deployment hooks, you can automate those tasks, ensuring your environments are consistent and deployment-ready every time.

🛠️ How it works

Hooks can be configured per repository. Once set up, GitPeeks will execute the defined hooks automatically during the deployment process. Read the docs for more information.

Introducing linked user accounts

GitPeeks now supports linked user accounts, allowing you to sign in once and switch between multiple user accounts.

🚀 What’s new?

You can now link multiple GitPeeks user accounts and switch between them without needing to sign in and out. Once accounts are linked, switching is fast and seamless—making it easier to manage multiple roles or organizations.

🤔 Why did we make this change?

Many users operate under different accounts for different projects—whether it’s personal use, teams, or client work. Until now, switching accounts meant logging out and back in. This update makes it simple to stay signed in to one account and hop between linked ones with ease.

🛠️ How it works

From the account or workspace popover, you can link both existing and new GitPeeks accounts. Once linked, a switcher will appear—allowing you to seamlessly switch between accounts without needing to reauthenticate. Signing in to any one of your linked accounts gives you instant access to all of them.

Automate Docker build cache prune

Prevent Docker build cache from filling up your server!

🚀 What’s new?

GitPeeks now automatically removes stale Docker build cache, preventing it from accumulating and taking up excessive disk space. This ensures that your server stays optimized without manual cleanup.

🤔 Why did we make this change?

Docker build cache can quickly grow over time, consuming valuable storage and potentially leading to build failures due to insufficient disk space. By automating cache pruning, we ensure that your servers remain clean and ready for new builds without requiring manual maintenance.

🛠️ How it works

• Define prune frequency in your server settings.

Set max build time for repositories

Take control of your builds with time limits!

🚀 What’s new?

Repositories can now define a maximum build time in GitPeeks. This ensures that builds don’t run indefinitely, allowing teams to set limits based on their needs.

🤔 Why did we make this change?

We introduced this feature to prevent unnecessary resource consumption and provide better control over build execution. Previously, builds could exceed expected durations, leading to wasted compute time and delayed feedback. With this update, teams can enforce time limits to keep workflows efficient and predictable.

🛠️ How it works

• Define max build time in your repository settings.

Introducing connected previews

We’ve introduced a new way to streamline testing when your app or service relies on separate repositories. This update empowers you to test end-to-end workflows in preview environments, eliminating the guesswork and enabling faster iteration.

🚀 What’s new?

You can now manage environment variables for previews, allowing your previews to communicate seamlessly. For example, a frontend preview can use a BACKEND_URL variable to point to the backend preview specific to your feature. This ensures you can test the entire workflow in a cohesive preview environment.

🤔 Why did we make this change?

Before this change, testing features that required changes in separate repositories was a challenge. Developers couldn’t fully test workflows without a manual workaround, leading to slower development and potential issues slipping through the cracks. This update simplifies the process, letting you focus on building and refining your features.

🛠️ How it works

• Define environment variables in your preview settings.
• These variables can be set at runtime to link your related previews.

✨ Key benefits

• Streamlined testing: Test end-to-end workflows effortlessly.
• Faster iteration: Focus on feature development with a simpler setup.

⚠️ Important notes

When environment variables change, a re-deployment of the preview is necessary.

Enhanced accessibility and responsive design

We’ve rolled out several improvements focused on accessibility, consistent spacing, and a more responsive user experience.

🚀 What’s new?

• Set viewport maximum scale: We’ve updated the viewport settings to include a maximum scale, improving accessibility for users who rely on screen magnification.
• Consistent margins: Margins have been refined across the app for a more polished and consistent look, ensuring a visually harmonious layout.
• Deployment log responsiveness: The deployment log now adapts beautifully to various screen sizes, making it easier to review logs on any device.
• Improved tabs and breadcrumbs: Tabs and breadcrumbs have been enhanced for better usability and appearance on smaller screens.
• Additional responsive updates: Further tweaks ensure the app is fully optimized for all screen sizes, delivering a seamless experience no matter the device.

🤔 Why did we make this change?

These changes improve the app’s usability and accessibility, ensuring a consistent and user-friendly experience for all. Whether you’re managing deployments or navigating complex workflows, the app now feels more intuitive and responsive.

Try out the improved design today and enjoy a more accessible and adaptable experience!