With the introduction of stacks last week, we implemented a pretty basic download experience that grouped the repositories into a single download and didn't allow customization (such as selecting a specific version) on a per repository level. This week, we upgraded that experience by granting developers the ability to customize each download (or clone) within a stack. The outcome offers a more precise download and cloning experience that reflects the real-world application of a stack.

• Improved downloads
• Improved clones
• Updated CLI / Docs
• Updated Docs

A screenshot of downloading a stack on Playbooks

As shown in the image above, when developers go to download a stack, they can now modify the version for each specific repository. This functionality was already available when downloading a individual repository. Now, it is supported when downloading a stack as well.

A screenshot of cloning a stack on Playbooks

As shown in the image above, when developers go to clone a stack, they can now modify the repository name, version and privacy. This functionality was already available when cloning a individual repository. Now, it is supported when downloading a stack as well.

A screenshot of cloning a stack on Playbooks

As part of this update, we updated the Playbooks CLI so developers can download (or clone) a stack directly from their terminal or any machine using the @playbooks/cli SDk along with their credentials. To learn more about using the API or CLI, please visit the Playbooks Docs website.

If you made it this far, thank you for taking the time to catch up on what's happening at Playbooks! To receive these updates in your inbox, simply create a account over on Playbooks. Or, feel free to follow along over on Twitter / X to receive updates there.