v1.2.0

What's new in 1.2.0

This is a minor release because it adds a new command and new checks. It covers everything since 1.1.0, and has the same code as 1.1.2-beta.0.

npm install -g @agility/cli@latest

New features

• verify command — agility verify --sourceGuid A --targetGuid B compares a synced target with its source and reports what differs. It checks:

  • content (counts per model and container, list order, field values with linked content and assets resolved through the mappings);
  • component order and zone placement on every page;
  • page tree and sitemap order per locale and channel;
  • models, containers, templates, assets, galleries, and mapping integrity.

  It never writes to either instance or to the mapping files. Exit codes: 0 match, 1 differences, 2 couldn't verify. It accepts --locales, --channel, --models, --pages, --containers and --jsonSummary. (PROD-2552, #235)

• Required-field validation before sending — content items are checked against the target model first. An item missing a required scalar field (Text, LongText, HTML, Integer, Decimal, Date, DropdownList, Boolean) is skipped and reported with the model and field names, so it no longer fails in the batch with a database error. Empty values, over-length text and unknown dropdown values only warn. --preflight lists these items under a new invalid action, which doesn't change the exit code. (PROD-2542, #234)

• Foreign CDN warning — sync, push and --preflight now warn when content references an asset URL in a CDN container that belongs to neither the source nor the target, for example content carried over from an older instance. Such URLs can't be mapped, and image fields that use them may arrive empty on the target. Each URL is listed once with every item, field and locale that uses it. This doesn't change counts or exit codes. (PROD-2773, #236)

• Auto-publish covers other locales — a page's components are shared by all of its locales, so a save that adds, removes or reorders components in one locale puts the page in staging in its other locales. With --autoPublish=pages|both, those pages are now republished in that locale too, when they were published before the run and are published in the source. Without auto-publish they're listed as warnings. (PROD-2782, #237)

Fixes

• Batch results matched to the wrong item — batch results are now matched to the items that were actually sent. If the counts don't line up, the whole batch is reported as unverifiable instead of guessing, and failures name the right item. (PROD-2542, #234)
• Failures labelled across locales — a content failure in one locale no longer marks the same content in another locale as failed. "Unresolved content reference" messages now name the skipped child and say why it was skipped. (PROD-2542, #234)

--jsonSummary additions

These are additive; the schema version doesn't change.

• warnings entries can carry code, url, container and references (code foreignCdnReference).
• Preflight totals and phases include an invalid count.
• autoPublish.warnings can include entries of type staging.

Works with the latest platform fixes

Two Agility platform fixes (no CLI change needed) remove the main sources of page differences that agility verify found after multi-locale syncs:

• saving a page in one locale no longer removes components that only exist in another locale (PROD-2776);
• linking a new locale to a page no longer places shared components twice (PROD-2774).

Full changelog: v1.1.0...v1.2.0