Releases: averenium/Ave-Nuget-Manager
Releases · averenium/Ave-Nuget-Manager
Release list
v0.8.0
Added
- Implemented multi TFM projects. Update no longer collapses a package pinned per target framework onto one version: each framework gets its own row, target, write and install (#82)
Fixed
- Hovering a row no longer washes out its selected colours, and High Contrast themes no longer show a hardcoded dark fill where they define none (#108)
v0.7.5
Added
- Package details: a transitive package lists the projects that pull it in, each with a one-click direct reference at the restored version (#90)
- Packages and Log: Ctrl+F (Cmd+F) focuses that tab's search box and selects what is already in it (#93)
- Install and remove show progress beside the Projects heading, held through the refresh that follows (#104)
Fixed
- Every version picker shows a dropdown arrow, and inputs and dropdowns answer hover, focus and being open the same way (#99)
- Updates: the family target selector marks vulnerable and deprecated versions, naming the members each mark came from (#92)
- Package search no longer launches
dotnetfor a config file that cannot answer — no sources, or folder sources without the package (#91) - Install has its own icon instead of the downgrade arrow, and the action buttons answer the pointer (#88)
- The development-only hot-reload watcher no longer runs in an installed extension, where it could fail activation on Linux (#95)
v0.7.0
Added
- Package details: the Info panel is built from the local
.nuspecandproject.assets.jsoninstead of a feed search — authors, licence, source and commit links and target frameworks beside the description, and a Dependencies list showing each declared range against the version actually resolved (#86)
Fixed
- A comment mentioning a tag or single-quoted attributes (both valid XML) could hide or duplicate a
nuget.configentry, or corrupt a non-SDK.csprojon save (#85)
v0.6.1
Added
- Agent skill (Dependency breaking-changes review, bumped to
1.1.0): a bundledscripts/review.fsxrun viadotnet fsi—diff,graphandnotescollect the manifest diff, the restore graph and every changed package's release notes for a pending bump, and write a report skeleton the agent fills in. Needs no GitHub token (#67) - Docs: new
docs/vulnerability-script.md— theaverenium.nugetManager.vulnerabilityScriptprotocol, with JavaScript and Python examples (#69) averenium.nugetManager.vulnerabilityScriptalso runs.fsx(dotnet fsi),.csx(dotnet script) and managed.dll(#69)- Docs: README reworked as a landing page for the VS Code Marketplace and Open VSX — what the extension replaces, a quick start, an install table per editor, and a screenshot slot per feature (shot list:
docs/marketplace-assets.md) (#84) - Marketplace search terms:
descriptionrewritten andkeywordsexpanded from 5 to 23 (#84) - Demo:
demo/— anExample.Shopsolution built for the listing screenshots: five .NET 10 projects, outdated packages throughout, two package families, five real advisories including a transitive one, aRabbitMQ.Client6.x pin and a two-sourcenuget.config(#84)
Fixed
- Log: Copy sanitised now masks project names too, using the same
pNN.csprojaliases as a trace zip (#65) - Log: expanded-row and toolbar polish — no duplicate Copy on non-CLI entries, repositioned hover-copy button, and the "N new ↓" pill no longer scrolls away (#66)
- Selecting a not-installed package no longer shows the version picked for a different package (#59)
- The source filter dropdown now closes on an outside click, Escape, blur, or scroll (#70)
- Moving the panel between locations replays the last state from cache instead of forcing a full restore, list and vulnerability scan (#71)
dotnet list/--vulnerabletimeout now scales with the project count (30s to 120s), with one retry after a timeout (#72)- The version list is seeded from cached enrich data instead of blanking to "Loading…" on every package selection (#76)
- Hover states add an outline so they stay visible in High Contrast themes (#68)
- Groups: the right-hand detail panel no longer blanks (name, version selector, package list) right after a group update succeeds, including when the same family is split across projects pinned to different versions
v0.5.0
Added
- A per-project row briefly flashes (green for an upgrade, amber for a downgrade) when its version change actually lands, respecting
prefers-reduced-motion(#56) - Package detail panel: generalized the Vulnerabilities section into a Problems section that also explains a
packageSourceMappingmismatch (which sources are mapped, why none match) and a blocked-updates state — previously those only showed as a bare row-mark tooltip with no detail (#57) - Log tab redesign (#58, subsumes #50/#51/#52): a
kind(cli/edit/scan/info/error) badge per row, withargsrendered for the previously content-free synthetic rows (edit PackageReference,nuget.config …,vulnerability scan skipped); an in-panel search over command/args/output plus an All/Errors/CLI/Edits filter, since VS Code's own Ctrl+F cannot reach a sidebar view; day separators between entries from different days; a failure-aware one-line preview (viasummarizeDotnetFailure) instead of a truncated stdout/stderr dump, with the full command, ordered stdout/stderr, and a clickableNU‑codechip once expanded; Copy, Copy sanitised (same redaction as a trace zip, for pasting into a public issue), and Open Output (the previously unreachable unbounded Output Channel) toolbar actions;Logger.info/Logger.errornow also produce a Log-tab row instead of being Output-Channel-only; and a 500-entry ring buffer (host and webview) so a long session doesn't grow memory unbounded — the Output Channel remains the unbounded sink.
Not folded into this pass: correlating a batch update's ~2N rows under one job/group (#58 finding #5) would need a job id threaded through the whole install pipeline (INuGetBackend/CliBackend/cliRunner signatures) — left for a follow-up given the size of this change already.
Fixed
- Vulnerabilities didn't recheck reliably after an install/update: the restore-text fallback stayed pinned to the last explicit Restore, an audit-source change didn't trigger a rescan, a row could show a different project's finding for the same package id at another version (e.g. seen only transitively through a
<ProjectReference>), and the fallback path trusted an already-stale--no-restorepackage list instead of re-restoring the solution/folder first (#53) - Update/Install button icons (Packages detail, per-project rows, Groups) always showed ↑/↓ regardless of whether the picked version was actually an upgrade, a downgrade, or unchanged — they're now direction-aware, and the button itself looks inactive (muted, not accent-colored) when the picked version already matches what's installed (#55)
- Remove buttons in Packages (detail panel and per-project rows) used a plain ✕ instead of the trash icon already used in Sources, and rendered with the always-red
.btn--dangerstyling — now the shared trash icon, muted at rest and red only on hover, matching Sources (#60) - The ↑/⊘/⚠/∅ row marks sized and positioned their pill off each glyph's own font-dependent metrics, so they rendered as differently-sized circles with the symbol sitting off-center inside the ring (worst for ⚠) — replaced the Unicode glyphs with small fixed-coordinate SVG icons, the same approach already used for the Sources trash icon, so centering no longer depends on font/platform (#60)
- Log: a new entry always auto-scrolled to the bottom, yanking the view away while reading an earlier one — it now only scrolls if the view was already at the bottom, otherwise a "N new ↓" pill appears (#51)
- Log:
toLocaleTimeString()followed the VS Code UI language rather than being explicit — entry times are now a fixedHH:mm:ss.SSS, independent of locale, with the full ISO timestamp in a tooltip (#52)
v0.4.2
Changed
- No longer marked Preview on the Marketplace — dropped the
previewflag and the leftover "(preview)" wording in the README's Install / Known limits sections.