Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unpublish specific version on VS Marketplace #846

Closed
amit-kulkarni-in opened this issue Mar 6, 2023 · 7 comments
Closed

Unpublish specific version on VS Marketplace #846

amit-kulkarni-in opened this issue Mar 6, 2023 · 7 comments
Assignees
Labels
under-discussion Issue is under discussion for relevance, priority, approach

Comments

@amit-kulkarni-in
Copy link

VS Marketplace allows extension authors to upload the extensions through CLI (vsce command) and Gallery UI in the publisher manage page. Currently in both the scenarios we support deleting at the extension level but not at the extension version level. This has been one of the top asks from the extension author community in marketplace github

Below are usescases for deleting specific version :
Use case 1:  An author noticed the latest version of their extension includes a serious bug but cannot find its cause soon. Currently, end users download the broken version until the author fix the bug and publish a new version. If the feature described above is implemented, the author can unpublish the latest one soon and set about bug fix without hurrying.

Use case 2: We are doing beta releases, and we would like to unpublish previous beta versions that are not usable anymore anyway.

Use case 3: Extension author accidentally uploads the VSIX file with secrets. Wants to delete the specific version which has secrets.

Current Implementation :
Currently publisher doesn’t have an option to delete the specific version they have to reach out to VSMarketplace@microsoft.com support alias to get the version deleted.

Some publishers have accidently used vsce unpublish <extension name> <version> thinking it would delete the specific version but have accidently deleted the complete extension (Github issue )

Recommendation implementation :

New CLI :
Due to the confusion and accidental delete possibilities of vsce unpublish command, can we have new CLI which allows only version to be deleted.
vsce delete <extension name> -version <version number>
Note that it is mandatory to provide version number.
@isidorn @prashantvc

@isidorn
Copy link
Contributor

isidorn commented Mar 7, 2023

@amit-kulkarni-in thanks for opening this feature request and for nicely documenting it.

@joaomoreno it looks like there are Marketplace API to unpublish a specific version and we should consider surfacing this in vsce - since extensions authors really want this. We can discuss in more detail in our next sync.

@joaomoreno
Copy link
Member

@isidorn Are you sure there are Marketplace APIs for this?

@joaomoreno joaomoreno added the under-discussion Issue is under discussion for relevance, priority, approach label Mar 7, 2023
@joaomoreno joaomoreno self-assigned this Mar 7, 2023
@joaomoreno joaomoreno closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2023
@tooltitude-support
Copy link

tooltitude-support commented Oct 27, 2023

It looks like it's not even in API, it's in officially documented and published API of Azure Devlops, not something internal to Microsoft: https://learn.microsoft.com/en-us/javascript/api/azure-devops-extension-api/galleryrestclient#azure-devops-extension-api-galleryrestclient-deleteextension

UPD: I tried this API with my PAT, and it didn't work. So API there, and either doesn't work or I am using it incorrectly.

cc @joaomoreno

@tooltitude-support
Copy link

tooltitude-support commented Oct 27, 2023

P.S. I did add a new command to the vsce code like other commands work. On invocation the error was:

  statusCode: 400,
  result: { count: 1, value: { Message: 'The request is invalid.' } },

@isidorn
Copy link
Contributor

isidorn commented Oct 30, 2023

@tooltitude-support I suggest to open a new issue, so we do not loose your investigation.

@tooltitude-support
Copy link

@isidorn Done: #909

@gee4vee
Copy link

gee4vee commented Dec 6, 2024

Why is this not planned? Seems like a pretty important feature.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

5 participants