2.1.0 - #8
Merged
Merged
Conversation
Both GPU readings were wrong on Apple Silicon, and the dependencies that shipped alongside them carried eleven command injection advisories. The changelog gained entries for the dependency work, which the pull requests that did it had not written down. That matters most for disk space: the percentage and the free-space figure both change meaning, and the old numbers were optimistic rather than merely different, so anyone upgrading will see them move. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Release commit for 2.1.0: bumps the manifest and closes the changelog section, so the tag has something to agree with.
Why 2.1.0 rather than 2.0.1
Nothing was removed and no setting changed, but several displayed figures now mean something different — the GPU utilization percentage, the GPU memory pair, and both disk figures. That is more than a patch admits to.
Changelog additions
The GPU section was already written. This adds the dependency work, which #6 and #7 landed without recording, and one item there is genuinely user-visible:
Disk figures change, and the old ones were wrong. The percentage is now used ÷ (used + available) as
dfreports it, rather than used ÷ size, and free space comes from the volume's ownavailablerather thansize - used. On APFS every volume reports the whole container as its size, so the old figures flattered:Anyone upgrading will see these move, sometimes a long way. Worth being explicit about rather than letting it look like a new bug.
Verified before tagging
npm run lintclean,npm auditreports 0 vulnerabilitiesvsce packagesucceeds — 44 files, 501 KBsysteminformationis present in the VSIX (24 files undernode_modules/systeminformation/lib/), which is the guard the release workflow enforces after a past release shipped without ittslintand the other dev dependencies are correctly absent from the packageOnce merged,
v2.1.0gets tagged and pushed, which triggers the publish.🤖 Generated with Claude Code