Skip to main content

​
Bug fixes

  • update.skip no longer leaves breaking-release upgrades half-migrated. Previously, projects with paths under update.skip in .trellis/config.yaml upgraded inconsistently across 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. 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:
    1. safe-file-delete migrations
    2. New file writes (e.g. the 0.5.0 continue.md command)
    3. Template updates for existing files (e.g. 0.5.0 finish-work.md)
    User customizations are still guarded — the per-file “Modified by you” confirm prompt still fires at write time. And the hash check in allowed_hashes is still the ultimate safety net for safe-file-delete (hash-mismatch files stay put with a skip-modified warning regardless of bypass). Non-breaking updates continue to respect update.skip exactly as before — only breaking releases trigger the bypass. 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.
No project file migrations in this release — pure CLI-side fix.

​
Migration

If your 0.4.x → 0.5 beta.2 upgrade left update.skip-protected paths half-migrated (old commands and skills sitting next to new ones), this release will finish the job: 
trellis update --migrate
You’ll see the yellow ⚠ update.skip BYPASSED notice listing the files that will finally get cleaned up. Install: npm install -g @mindfoldhq/trellis@beta