Skip to main content

Release Validation and Deploy Warnings

· 2 min read
Skpr Platform Team
Skpr Platform Team
Platform Engineering

Overview​

We've introduced improvements to how skpr validate and skpr deploy handle warnings.

These changes are designed to surface issues early, particularly in CI workflows, before they make it into a deployment.

Changes​

Validate now exits with an error on warnings​

Previously, running skpr validate <env> would exit successfully even if your site had warnings. As of v1.9.0, warnings will cause the command to exit with a non-zero status, making it easier to catch issues early in CI pipelines.

skpr validate dev

Deploy blocks on warnings​

If your site has warnings, skpr deploy <env> will now throw an error and refuse to deploy. Violations and warnings will be printed on failure so you can see exactly what needs to be addressed.

skpr deploy dev

Bypassing warnings​

If you've reviewed the warnings and are happy to proceed, you can bypass them using the --ignore-warnings flag:

skpr deploy dev --ignore-warnings

Note: Violations cannot be bypassed — only warnings.

What triggers a warning?​

Warnings are raised for significant configuration changes, such as removing a domain name from an environment. The set of conditions that trigger warnings will be updated with each Skpr minor release as required.