Hi everyone! Here’s what landed in CloudCannon over the last month, headlined by Deploy Previews.
Deploy Previews for Pull Requests
You can now set up Deploy Previews from the Project Settings page. They run automations whenever a Pull Request is opened, updated, merged, or closed in your connected Git Repository, and they’re available on the Team or Enterprise plan.
There are two options:
- Automatic Sites creates a CloudCannon Site for each Pull Request. You can exclude draft Pull Requests and automatically delete the Site when the Pull Request is merged or closed.
- Automatic Comments posts a comment on each Pull Request with the build status, Testing Domain, Site Dashboard, and build logs for every CloudCannon Site connected to that branch. You can exclude draft Pull Requests and add your own markdown to the comment footer.
For the full rundown, read our documentation on Deploy Previews.
Two new Project tabs: Pull Requests and Branches
We added two optional Project tabs you can switch on from the Project Settings Details page. The Pull Requests tab shows all open and draft Pull Requests in your connected Git Repository, and the Branches tab shows your branches alongside every CloudCannon Site connected to each. See our documentation on optional Project tabs.
Enforce MFA on the Team plan
You can now require Multi-factor Authentication for everyone in your Organization on the Team plan, not only Enterprise.
Set a minimum TLS version for your domain
Domain Settings now has a TLS section where you can set a single minimum TLS version (1.2 or 1.3) for every Site on a Domain. For more information, read our documentation on increasing the minimum TLS version for your domains.
A warning when a Schema can’t be found
CloudCannon now warns you when it can’t find the Schema for a file, and it won’t open the file in an Editing Interface if the Schema is incorrectly defined. This protects your content from unintended changes to its data structure. We also added support for .astro Schemas.
Try CloudCannon’s Astro agent skills
We added prompts to try CloudCannon’s agent skills for creating and configuring Astro Sites with AI. You’ll see a prompt on the Create a Site page, and when syncing an Astro Site from a Git Repository you can tick Set up with local AI agent instead of in-app for terminal instructions.
Bigger uploads
The maximum upload capacity per Site went from 50 MB to 100 MB.
Source Editor and browser performance
The Source Editor now shows vertical indentation lines to make nesting clearer. We also sped up the Project Sites Browser, especially for Organizations with custom Permission Groups and many Exceptions, and the Project Browser, Site Browser, Branches, and Pull Requests now default to sorting by last synced.
A few other things worth mentioning
- Client Sharing Login URLs now show a clearer error message when the feature is disabled by a plan or billing change.
- Fixed Delete after publishing not triggering when you published a Pull Request from your Git Provider rather than from CloudCannon.
- Fixed builds failing for Sites using the legacy i18n feature.
- Fixed Invoices sorting oddly — they now order newest first.
- Fixed being unable to disable enforced MFA, and fixed some cases where accepting an invitation to an Organization requiring MFA or SSO rerouted you away from Account Settings.
- Fixed Data Panels in the Visual Editor rendering an Input’s comment and documentation link twice.
- Plus fixes for WYSIWYG toolbar tooltip delays, drag-and-drop in the Multiselect Input, unresponsive pages in Safari, and various UI spacing issues.
That’s it for June! As always, let us know what you think or if you have any questions, and reach out to our support team if you need a hand. 