Skip to content

fix: improve update tool output for Fresh 2 projects#3754

Merged
bartlomieju merged 2 commits intomainfrom
fix/update-scary-output
Apr 9, 2026
Merged

fix: improve update tool output for Fresh 2 projects#3754
bartlomieju merged 2 commits intomainfrom
fix/update-scary-output

Conversation

@bartlomieju
Copy link
Copy Markdown
Member

Summary

  • Detects whether a project is already on Fresh 2 by checking deno.json imports
  • Shows "Updating Fresh to X.Y.Z..." instead of "Starting Fresh 1 to Fresh 2 migration..." for existing Fresh 2 projects
  • Only shows "Breaking changes may require additional manual updates" warning for actual Fresh 1→2 migrations
  • Summary/completion messages adapt accordingly ("Update" vs "Migration")

Closes #3688

Test plan

  • Existing update tests pass (16/16)
  • Run @fresh/update on a Fresh 2 project and verify the output says "Updating" not "Migrating"
  • Run @fresh/update on a Fresh 1 project and verify it still shows migration messaging

🤖 Generated with Claude Code

bartlomieju and others added 2 commits April 8, 2026 19:31
The updater now detects whether a project is already on Fresh 2 and
adjusts its messaging accordingly. Fresh 2 patch/minor updates no
longer show "Starting Fresh 1 to Fresh 2 migration..." or the
breaking changes warning.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@bartlomieju bartlomieju merged commit c0a866d into main Apr 9, 2026
9 checks passed
@bartlomieju bartlomieju deleted the fix/update-scary-output branch April 9, 2026 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fresh auto-update output is too scary

1 participant