feat: report repo-bootcamp version in bootcamp doctor#61
Merged
Conversation
`bootcamp doctor` diagnoses Node, git, gh, auth, mermaid, and cache, but
never surfaced which version of the tool itself was running — the first thing
you want in a bug report. It now reports the running package version as the
leading info check ("repo-bootcamp: v1.2.3") and exposes it as
`environment.toolVersion` in `--json` output.
Also fixes a stray duplicate `### Added` header in the CHANGELOG Unreleased
section.
Tests: extended doctor unit tests (version info check + JSON toolVersion
field) and added a new doctor E2E spec (none existed) asserting the human
report shows the version and the JSON payload carries environment.toolVersion
and a `version` check.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
e8fe9e6 to
9ebcd72
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bootcamp doctordiagnoses Node, git, gh, auth, mermaid-cli, and cache health — but never reported which version of the tool itself is running, which is the first thing you want in a bug report or support thread.It now reports the running package version as the leading info line:
and exposes it as
environment.toolVersion(plus aversioncheck) in--jsonoutput.Also fixed
A stray duplicate
### Addedheader in the CHANGELOG's Unreleased section (a merge artifact) is cleaned up in this PR.Implementation
toolVersionto the pureEnvironmentSnapshot(sourced frompackage.json, the same waycli.tsreads the version).evaluateDoctoremits a leadingversioninfo check — info severity, so it never affects the pass/fail outcome.Testing
versioninfo check and the--jsonenvironment.toolVersionfield.repo-bootcamp: vX.Y.Zand the JSON payload carriesenvironment.toolVersionand aversioncheck.npm test→ 1129 passing; typecheck + lint + build clean.🤖 Generated with Claude Code