Skip to content

chore: bump CommandLineParser from 2.7.82 to 2.9.1#169

Open
Aiudadadadf wants to merge 1 commit intotporadowski:developfrom
Aiudadadadf:chore/bump-commandlineparser-2.7.82-to-2.9.1
Open

chore: bump CommandLineParser from 2.7.82 to 2.9.1#169
Aiudadadadf wants to merge 1 commit intotporadowski:developfrom
Aiudadadadf:chore/bump-commandlineparser-2.7.82-to-2.9.1

Conversation

@Aiudadadadf
Copy link
Copy Markdown

Bumps CommandLineParser from 2.7.82 to 2.9.1 in msvs/ReleasePackagingTool.

Changes: packages.config version updated from 2.7.82 to 2.9.1; ReleasePackagingTool.csproj HintPath and reference version string updated to match.

The tool uses only [Option] attribute declarations and the Parser.Default.ParseArguments<T>().WithParsed() fluent call - both are part of the stable public API that CommandLineParser has kept unchanged since v2.0. The 2.8 and 2.9 releases added async overloads, verb aliases, and flag enum support; nothing was removed or changed in the synchronous path this project uses. The PublicKeyToken and target framework (net45) remain the same.

Updates the CommandLineParser NuGet reference in ReleasePackagingTool
from 2.7.82 to 2.9.1 (latest stable).

- packages.config: version 2.7.82 -> 2.9.1
- ReleasePackagingTool.csproj: HintPath and Reference version updated

No API changes affect this project: only [Option] attributes and
Parser.Default.ParseArguments<T>().WithParsed() are used, both of
which are unchanged across 2.7 -> 2.9.
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.

1 participant