jessehouwing/VS Marketplace
Publish Visual Studio extension to the Visual Studio Marketplace
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| operation | Operation to perform: publish or package | no | publish |
| auth-type | Authentication type (pat or oidc) | no | pat |
| token | Personal Access Token for Visual Studio Marketplace (required when auth-type is pat) | no | — |
| vsix-file | Path to the VSIX file to publish (required when operation is publish) | no | — |
| manifest-file | Path to the publish manifest file (required when operation is publish) | no | — |
| publisher-id | Publisher ID for the extension (required when operation is publish) | no | — |
| ignore-warnings | Comma or newline-separated list of warnings to ignore (e.g., VSIXValidatorWarning01,VSIXValidatorWarning02) | no | — |
| vsix-manifest | Path to the .vsixmanifest file (required when operation is package) | no | — |
| output-path | Output path (directory or full .vsix path) for the packaged extension (required when operation is package) | no | — |
| files-manifest | Path to the files.json manifest listing extension content files for packaging. Generated by the MSBuild GenerateFileManifest target (dotnet msbuild -t:GenerateFileManifest). If omitted, the tool uses the files referenced by the VSIX manifest. | no | — |
| working-directory | Working directory used as the base path for manifest-based operations. - Manifest discovery and file paths are resolved from this directory - Use this when your extension manifest lives in a subfolder - If not specified, the current working directory is used Example: tests/sample-extension | no | — |
Outputs
| name | description |
|---|---|
| vsix-file | Full path to the packaged .vsix file (set when operation is package) |