Skip to content

v1.0.2

Choose a tag to compare

View all tags
@5PK 5PK released this 02 Oct 14:49
· 10 commits to main since this release
v1.0.2
29d1ad8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Re-released as v1.1.0. This release adds new features, so it should have been a minor version. Install 1.1.0 or later instead of 1.0.2.

What's new in 1.0.2

This promotes 1.0.2-beta.4 to stable. It covers everything since 1.0.1.

npm install -g @agility/cli@latest

New features

  • reverse-sync command — agility reverse-sync --sourceGuid A --targetGuid B pushes the original target (B) back into the original source (A). It reuses the forward sync's mapping files in mappings/A-B/ instead of creating a second set, and saves a backup of them to mappings-backups/A-B/{timestamp}/ before the first write. (PROD-2526, #212)
  • Sync selected pages with --pages — pushes one page structure and its child pages and nothing else, e.g. --pages="/my-page". (PROD-2546, #219)
  • --jsonSummary=<path> — writes a JSON record of a sync run (counts, failures, exit code) for scripts and CI. (PROD-2557, #215)
  • --fullPull (alias --full-pull) — discards the sync token and does a full content pull. Pulls now also remove local files for templates, galleries, assets, content items and pages that were deleted upstream, so the local cache matches the instance. (PROD-2614, #224)

Fixes

  • Orphan items created on every run — when a mapping pointed at a target item that had been deleted or unpublished, the CLI made a new item on every run without repointing the mapping. That case is now treated as a target-side change. (PROD-2603, #220)
  • Deleted target templates were recreated — a mapping to a template that had been deleted on the target is now reported as a conflict instead of quietly recreating the template. --overwrite still recreates it. (PROD-2603, #226)
  • Models re-pushed when nothing changed — model change detection now compares the source model against the date recorded at the last sync instead of the target's date, and models with identical structure are skipped. This stops models and containers being pushed back and forth between instances. (PROD-2604, #221)
  • Page conflicts after multi-locale saves — saving a page in one locale can change its version in other locales. Those versions are now refreshed after the save, so the next run no longer reports a false "target has been changed independently" conflict or sends pages back and forth under reverse-sync. (PROD-2628, #228)
  • Duplicate asset uploads — when a mapped target asset was missing or had been moved to another folder, the CLI uploaded a second copy and added a duplicate mapping record. It now repoints the existing mapping instead. (PROD-2627, #230)
  • Asset, gallery and redirect failures missing from reports — these failures now appear in the --jsonSummary failures list and in the console ERROR SUMMARY instead of only as a count. (PROD-2629, #229)
  • Failures logged at the wrong level — sync failures are now logged at ERROR and conflicts at WARN (they were all INFO), and items skipped during the content phase now appear in the log. (PROD-2533, #213)

Other changes

  • Console and log output now say "Component" instead of "module", to match the Agility app. This changes output text only. (PROD-2534, #214)
  • Removed dead code and unused dependencies. (#209)

Full changelog: v1.0.1...v1.0.2

Assets 2
Loading