Changelog

This release added better error messaging on Client Sharing Login URLs.

It also addressed several issues, including those affecting Data Panels in the Visual Editor, the Project Branch Link in the Site Header, Invoice ordering, the Permissions tab on the Client Sharing page, Org Cards in the Organization Browser, and the TLS section of the Domains Settings.

Features & Improvements

• Better error messaging on Client Sharing Login URLs when the feature is disabled due to a change in Subscription Plan or billing state.

Fixes

• Fixed an issue where Data Panels in the Visual Editor rendered the Comment and Documentation Link of an Input twice.
• Fixed an issue causing the Project Branch Link in the Site Header to be incorrect.
• Fixed an issue where Invoices were ordered by year ascending, then by month descending. Invoices are now ordered by newest first (year and month descending).
• Fixed an issue where the Permissions tab on the Client Sharing page under Site Settings did not appear disabled if you did not have permission to edit it.
• Fixed an issue causing incorrect UI spacing for Org Cards in the Organization Browser when a Partner Organization required MFA.
• Added minor UI fixes for the TLS section of the Domains Settings tab.
• Updated dependencies to patch security vulnerabilities.

This release introduced the Deploy Previews feature, added optional Project tabs, and added minimum TLS version configuration for all Sites on a domain.

Features & Improvements

• Added Deploy Previews to the Project Settings page, which run automations whenever a Pull Request is opened, updated, merged, or closed in your connected Git Repository. This feature is available on the Team or Enterprise plans. For more information, please read our documentation on Deploy Previews.
  • The Automatic Sites option creates a CloudCannon Site for each Pull Request. You can configure this behavior to exclude draft Pull Requests and delete the Site when the Pull Request is merged or closed.
  • The Automatic Comments option posts a comment on each Pull Request with the build status, Testing Domain, Site Dashboard, and build logs, for each CloudCannon Site connected to the Pull Request branch. You can configure this behavior to exclude draft Pull Requests and add custom markdown content to the comment footer.
• Added two new optional Project tabs: Pull Requests and Branches. You can enable these tabs using the Optional Project Tabs switches on the Project Settings Details page. For more information, please read our documentation on optional Project tabs.
  • The Pull Requests tab on the shows all open and draft Pull Requests in the connected Git Repository.
  • The Branches tab on the shows the branches in the connected Git Repository and all CloudCannon Sites connected to each.
• Added a TLS section to Domain Settings, which allows you to set a single minimum TLS version (1.2 or 1.3) for every Site on a Domain.

Fixes

• Updated dependencies to patch security vulnerabilities.

This release added a warning for incorrectly defined Schemas, support for .astro Schemas, and vertical indentation lines to the Source Editor.

It also addressed several issues, including those affecting WYSIWYG Toolbar Tooltips, Sites using the legacy i18n feature, dragging in the Multiselect Input, and disabling enforced MFA.

Features & Improvements

• Added a warning when CloudCannon cannot find the Schema for a file. CloudCannon will no longer open files in the Editing Interface when the Schema is incorrectly defined, protecting your content from unintended changes to a file's data structure.
• Added support for .astro Schemas.
• Added vertical lines to the Source Editor to improve the visual clarity of line indentation.

Fixes

• Fixed an issue causing a delay before the Tooltip appeared when hovering a tool in the WYSIWYG Toolbar of the Content Editor or a Rich Text Input.
• Fixed an issue causing builds to fail for Sites using the legacy i18n feature.
• Fixed an issue where you could not drag items inside a Multiselect Input.
• Fixed an issue where you could not disable the Require multi-factor authentication (MFA) for everyone in your organization option.
• Updated dependencies to patch security vulnerabilities.