New in Bunnyshell: Stacked PRs, environment lifecycle controls, and more
 ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍ ‌​‍


BUNNYSHELL PRODUCT UPDATES

What's new in Bunnyshell

We've shipped several updates to Bunnyshell, including support for GitHub stacked PRs, new environment lifecycle controls, and improvements to Docker builds and configuration workflows.

Here's what's new.

GitHub stacked PRs

Screenshot of the Bunnyshell interface showing a GitHub Stacked PRs menu detailing multiple related pull requests and environments.


Bunnyshell now supports GitHub stacked pull requests.

Each PR in a stack gets its own ephemeral environment, including PRs targeting other feature branches instead of the primary branch.

Stacks are detected automatically, with no additional configuration required.

You can view all environments belonging to a stack directly from the environment details page. As PRs are merged and the stack changes, Bunnyshell updates the associated environments and their stack positions.

Existing ephemeral environment settings, including automatic deployment and cleanup on PR close, also apply to stacked PRs.


More control over environment lifecycle

Availability Rules now support Auto-undeploy and Auto-destroy, alongside the existing timeframes and auto-stop options.

These controls let you automatically stop, undeploy, or destroy environments based on your configured rules, reducing unnecessary infrastructure usage.

We've also improved how ephemeral environments respond to PR changes:

  • Re-create on push: Enable Re-create ephemeral environment on Pull Request push to automatically recreate a previously deleted ephemeral environment when a new commit is pushed.

  • PR retargeting: When a PR's target changes to a branch tracked by a primary environment, Bunnyshell automatically creates the corresponding ephemeral environment.

Both workflows now work without closing and reopening the pull request.

Docker build additional contexts

Bunnyshell now supports build.additional_contexts for Docker Compose components and additionalContexts for Docker image components.

Builds can reference additional contexts from local directories, Git repositories, container registries, and other Bunnyshell components.

This makes it possible to share build dependencies across multiple services without duplicating Dockerfile stages or publishing intermediate images separately.

Faster configuration saves

Saving bunnyshell.yaml is now faster, particularly for environments with multiple components referencing different Git repositories and branches.

Repository and branch validation now runs in parallel instead of sequentially, significantly reducing the time required to save complex configurations.

Other improvements


Queued operations
Environment operations can now be queued from both the UI and CLI, making it easier to manage multiple operations without waiting for each one to finish.


YAML comments
Comments in bunnyshell.yaml are now supported and preserved when editing configurations.


Kubernetes 1.37
Added support for Kubernetes 1.37.


What should we improve next?

We're continuing to improve Bunnyshell based on how you use it.

If there's something missing from your workflow or something we could make better, just reply to this email. We'd love to hear from you.

Best,
The Bunnyshell team