Skip to content

fix: distinguish bundle downloads from updates - #330

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/update-source-status
Sep 8, 2026
Merged

Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/update-source-status

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

Summary

  • Distinguish bundle downloads, updates, refresh-cache actions, unchecked sources, pinned sources, and local changes in amplifier update reporting.
  • Keep aggregate mixed states and failure labels truthful, including completion verbs.
  • Add a short reporting convention and real Click-command regression coverage for the nine-source download scenario.

Verification

  • Full offline suite in the isolated target environment: 2067 passed, 3 skipped, 13 deselected, 1 xfailed in 20.65s.
  • Independent focused review: 60 tests passed.
  • Regression tests exercise the real Click command while mocking only external status/apply boundaries.
  • One initial environment-sensitive truststore check failed in an unisolated local run; a clean-environment rerun passed without source or package changes. This change does not alter truststore behavior.
  • No live reset, network update, LLM, or DTU run was used for this fix.

Scope

  • Reporting-only CLI change. Bundle discovery/inventory, startup, action selection, force handling, and exit semantics are unchanged.
  • CI expected: six unit-matrix jobs, two POSIX integration jobs, and the repository CLA check.
  • No breaking changes.

Generated with Amplifier

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
@bkrabach
Brian Krabach (bkrabach) merged commit bac559e into main Sep 8, 2026
9 checks passed
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