Skip to content

fix: quieten the update check and say how to recover a newer manifest - #99

Merged
marcossevilla merged 3 commits into
mainfrom
fix/update-check-and-manifest-guidance
Oct 28, 2026
Merged

marcossevilla merged 3 commits into
mainfrom
fix/update-check-and-manifest-guidance

Conversation

@ryzizub

@ryzizub ryzizub commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Description

Stack 2 of 5 for #68. Base: fix/clone-timeout (#98).

The update check asked pub.dev about a package that is not published, so every command ended with Failed to check for updates. Very Good CLI swallows the same failure; it is a best-effort check that should not be an error.

ReportingManifestStore now tells the user to run vgv_ai update when the manifest was written by a newer version, which only doctor did. --only lists what each harness is instead of bare enum names, --force is coloured like every other flag, and the resolver's git output reaches --verbose.

Also extracts commandHome, which three commands had inlined, and adds a shared TestRunner so the command tests stop declaring the same three mocks.

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore
  • 🧪 Test

🤖 Generated with Claude Code

@ryzizub
ryzizub added this pull request to stack #103 October 21, 2026 12:19
@ryzizub
ryzizub marked this pull request as ready for review October 21, 2026 12:20
@marcossevilla
marcossevilla force-pushed the fix/update-check-and-manifest-guidance branch from 11a0102 to dd8d757 Compare October 28, 2026 11:54
Base automatically changed from fix/clone-timeout to main October 28, 2026 11:55
The update check asked pub.dev about a package that is not published, so every
command ended with "Failed to check for updates." Very Good CLI swallows the
same failure; it is a best-effort check that should not be an error.

ReportingManifestStore now tells the user to run `vgv_ai update` when the
manifest was written by a newer version, which only doctor did. --only lists
what each harness is, --force is coloured like every other flag, and the
resolver's git output reaches --verbose.

Also extracts commandHome, which three commands had inlined, and a shared
TestRunner so the command tests stop declaring the same three mocks.
@marcossevilla
marcossevilla force-pushed the fix/update-check-and-manifest-guidance branch from dd8d757 to 226f4a9 Compare October 28, 2026 11:55
@marcossevilla

Copy link
Copy Markdown
Member

@vgvbot /address-review

@unicoderbot

unicoderbot Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

On it, I'll address the review comments and push the changes.

  • Preparing environment
    • Cloning repository
    • Setting up dev environment
  • Reviewing feedback
  • Working on changes
  • Pushing updates

I've pushed changes to address the feedback.

Co-authored-by: marcossevilla <marcossevilla@users.noreply.github.com>
@marcossevilla
marcossevilla merged commit 687ec08 into main Oct 28, 2026
6 checks passed
@marcossevilla
marcossevilla deleted the fix/update-check-and-manifest-guidance branch October 28, 2026 12:13
@vgvbot vgvbot mentioned this pull request Oct 29, 2026
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.

2 participants