{
  "version": "0.5.0-beta.3",
  "description": "Bug fix: update.skip no longer leaves breaking-release upgrades half-migrated — skip is bypassed for safe-file-delete and template writes when manifest is breaking + recommendMigrate + user passed --migrate",
  "breaking": false,
  "recommendMigrate": false,
  "changelog": "**Bug Fixes:**\n- fix(update): bypass `update.skip` across safe-file-delete + template writes for breaking releases. Previously, projects with paths under `update.skip` in `.trellis/config.yaml` would upgrade inconsistently when crossing a breaking release: `rename` migrations already ignored skip, but `safe-file-delete` and template writes honored it. Result: users ended up half-migrated — old deprecated files persisted under skip-protected paths, new commands like `continue.md` never landed, and every future update re-flagged the same mess.\n\n  Now when the current upgrade spans a manifest with `breaking: true + recommendMigrate: true` and the user passed `--migrate`, `update.skip` is bypassed for all three operations: rename / safe-file-delete / template writes. User customizations are still guarded by the per-file `Modified by you` confirm prompt at write time, and the hash check in `allowed_hashes` is still the ultimate safety net for safe-file-delete (user-modified files stay put with a `skip-modified` warning regardless).\n\n  Non-breaking updates continue to respect `update.skip` as before — only breaking releases trigger the bypass.\n\n  A new yellow `⚠ update.skip BYPASSED` notice appears in the breaking-change warning block so users aren't surprised when skip-protected files get cleaned up during the migration.",
  "migrations": [],
  "notes": "Pure CLI-side bug fix — no project file migrations. If upgrading from 0.4.x with an `update.skip` in config.yaml, this release finally lets the 0.5.0-beta.0 breaking migration complete cleanly: run `trellis update --migrate` to finish any half-migrated state from prior 0.5 beta upgrades."
}